Date: Fri, 9 Jun 2006 12:53:37 -0400 From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: "R. B. Riddick" <arne_woerner@yahoo.com> Cc: fs@freebsd.org Subject: Re: heavy NFS writes lead to corrup summary in superblock Message-ID: <200606091253.37446.mi%2Bmx@aldan.algebra.com> In-Reply-To: <20060609065656.31225.qmail@web30313.mail.mud.yahoo.com> References: <20060609065656.31225.qmail@web30313.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
п'ятниця 09 червень 2006 02:56, R. B. Riddick написав: > I say, does that discrepancy persist, when you just wait some time? Yes... I'm noticing this hours after the dumps ended... > I would guess, that something has an open file descriptor on a deleted > file, so that this file cannot be really deleted (it just disappears from > the directory tree)... If anything did, I wouldn't be able to umount the filesystem cleanly, would I? Yet, it unmounts peacefully, even though the subsequent fsck finds the superblock summary to be incorrect. When I tried to use the FS as a scratch for an unrelated thing, though, I noticed some processes hanging in nbufkv state. Google-ing led me to the: http://lists.freebsd.org/pipermail/freebsd-current/2003-June/004702.html Is this 3 year old advise *still* true? I rebuilt the kernel with BKVASIZE bumped to 64K (the block size on the FS in question) and am running another batch of dumps right now. When it is over, I'll check the df/du... Yours, -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606091253.37446.mi%2Bmx>