Date: Sat, 17 Jan 2004 06:29:50 -0800 From: Pete Carah <pete@altadena.net> To: current@freebsd.org Subject: Re: 5.2-RELEASE: Possible bug in filesystem code? Message-ID: <20040117142950.GA28573@users.altadena.net>
next in thread | raw e-mail | index | archive | help
I had observed many times over a long time two things: 1. The background fsck can easily cause a panic with a disk-intensive process going on, and it has not seemed to depend on available space for me. I have disabled background fsck in rc.conf on *all* my systems because of this. 2. The other source of a panic is if the background fsck detects a condition which would cause the "preen" fsck to abort and give the "run fsck manually" message at bootup, it (usually?) panics the system, usually with "freeing freed inode". I can't think of how to handle this case any better; this is a "hobson's choice" condition :-( -- Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040117142950.GA28573>