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: > > 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=NO (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
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:31 UTC