Date: Tue, 12 Oct 2004 13:57:36 -0400 From: Mikhail Teterin <Mikhail.Teterin@murex.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: bde@zeta.org.au Subject: panic in ffs (Re: hangs in nbufkv) Message-ID: <416C1B10.7030103@murex.com> In-Reply-To: <200410112038.i9BKcCWt051290@apollo.backplane.com> References: <416AE7D7.3030502@murex.com> <200410112038.i9BKcCWt051290@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote:
>:One of our file systems here does, indeed, use large block size (64K, I
>:think, not sure, how to verify it) -- it is used for storing large
>:database dumps. Are the bugs, Bruce and Matt are talking about, supposed
>:to be gone by now (in which case, I can provide more debugging info), or
>:does this remain a "known problem" and I should simply adopt the
>:workaround suggested by Bruce in the first link above -- increase
>:BKVASIZE? Should I also merge the patch posted by Bruce in the last of
>:the links above, or are there good reasons, it is not in the official tree?
>
>
[...]
> But to be absolutely safe, I would follow Bruce's original suggestion
> and increase BKVASIZE to 64K, for your particular system.
>
>
After doing this and testing our backup script, the machine panicked two
hours later (about half-way through the backup) with
"initiate_write_inodeblock_ufs2: already started" (in
ufs/ffs/ffs_softdep.c)... I guess, block sizes above 16Kb are just buggy
and newfs(8) should be honest about it...
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?416C1B10.7030103>