[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: stagger forced fsck on reboot

On Mon, Jun 19, 2006 at 04:40:05PM +1000, Drew Parsons wrote:
> Hi debian-installer people,
> Partitions have a counter so that an fsck is forced on them at reboot
> after they have have mounted as certain number of times (I think it's
> after 20 or 30 mounts).
> The last time I checked, on a default installation with multiple
> partition this forced fsck occured after the same number of mounts for
> each partition.  Personally I find this quite inconvenient for laptops.
> In my experience laptops are still relatively unstable.  The battery may
> run out,  after S3 sleep (suspend-to-ram) it may not always resume
> correctly (there have particularly been problems here with DRI on the
> X11 video driver my laptop uses).  So for a variety of reasons a laptop
> reboots and remounts partitions much more frequently than a desktop.
> The problem then is when the partitions hit the forced-fsck mark, with
> the default settings they all have to go through their fsck at the same
> time. It takes time, and when all you had intended to do was to resume
> out of suspend to quickly check some data, but came up against one of
> these laptop crashes, it can be quite annoying.

If that's what you're trying to do, then staggering the forced fsck timings
isn't going to help you at all.

fsck on boot can occur in two occasions: either it needs to be done
because you hit the max mount count or max unchecked timeout, or it
needs to be done because you previously umounted uncleanly and it can't
be fixed by replaying the ext3 journal (either because it got corrupted,
or because you're running ext2 and there is no journal).

Fun will now commence
  -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4

Reply to: