On Wed, 10 Feb 2010, Goswin von Brederlow wrote: > The suggestion here is far simpler. Just do it on boot like now and on > shutdown without ever blocking. That would mean that on boot under
What stops the time-based trigger from not being active when the shutdown would fsck, but becoming active in the next boot? A simple call to fsck after umounting filesystems would avoid triggering the max-mounts-since-last-fsck trigger on boot for everything but the root filesystem (which we can't umount), but fixing the two remaining boundary conditions ain't that easy (rootfs, and time-based fsck triggers). With some testing, maybe we can fsck the root on shutdown *when* we succeed at remounting it read-only (but we have to make sure the behaviour, should fsck find any errors, will be sane. And that does mean not changing a power off into a reboot, etc). For time-based triggers, the only fix I can think of is to disable them in the filesystem itself. Note that I am not against a partial fix at all, send the patches in :-) But it would be nice if we would change the installer and mkfs defaults to avoid enabling any time-based triggers by default. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100216154915.ge8...@khazad-dum.debian.net
