heavy NFS writes lead to corrup summary in superblock

[Konstantin Belousov]

On Thu, Jun 08, 2006 at 01:46:04PM -0400, Mikhail Teterin wrote:
> Our amd64 6.1-STABLE system is used to collect backup dumps from production 
> systems (mostly -- Solaris) via NFS. When in progrss, the dumps arrive at an 
> average rate of 20Mb/s.
> 
> Every once in a while I notice a discrepancy in the amount of used space on 
> the backup FS as reported by df vs. that reported by the total du.
> 
> Unmounting the FS and fsck-ing it fixes the problem with fsck reporting 
> (despite the clean unmount):
> 
> 	SUMMARY BLK COUNT(S) WRONG IN SUPERBLK
> 	SALVAGE? yes
> 
> The FS is intended for very few very large files and was created 
> with "newfs -b 65536 -O1" (no softupdates).
> 
> This workaround (explicit fsck) is acceptable for us, but it is a sign of some 
> kind of rot, and I thought, you'd like to know...
> 
> Yours,
> 
> 	-mi
Wild guess: try rev. 1.673 of the sys/kern/vfs_subr.c.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20060609/cb2f38c0/attachment.pgp