Date: Mon, 11 Apr 2005 17:42:32 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Dan Nelson <dnelson@allantgroup.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Softupdates not preventing lengthy fsck Message-ID: <20050412004232.GA83769@xor.obsecurity.org> In-Reply-To: <20050412003114.GD284@dan.emsphone.com> References: <20050411234512.GA23344@xor.obsecurity.org> <20050412003114.GD284@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 11, 2005 at 07:31:15PM -0500, Dan Nelson wrote: > In the last episode (Apr 11), Kris Kennaway said: > > I'm seeing the following problem: on 6.0 machines which have had a lot > > of FS activity in the past but are currently quiet, an unclean reboot > > will require an hour or more of fscking and will end up clearing > > thousands of inodes: >=20 > This might be expected behaviour if the previous boot tried to do a > bgfsck and failed. It should set a flag forcing a full fsck on the > next boot, which will clear out the half-committed inodes from the > previous crash. I see it often on 5.*. I should have mentioned that I have background_fsck=3DNO (because of too many filesystem corruption problems after panics). The previous time the system booted it also had to fsck, and did the same thing (it's now been running for >2 hours). Kris --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCWxl3Wry0BWjoQKURAsEyAKCgT+m+hohnXEfCghUFCK7qOhZpgQCglLxJ nmDdMC0WoKR1ifCVmUw/hl8= =Nb0Q -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050412004232.GA83769>