On Thu, 01 Jan 2009, Petter Reinholdtsen wrote: > Right. So you have been hit by the introduction of asynchronous > behaviour of the Linux kernel. I have no good idea how to solve it.
I do, but it is a lot of work, and dangerous too. 1. Have a rw in-mem store available before udev coldplug. We will add udev device+filesystem id strings to it when filesystems are fsck'd. Note: colisions means a filesystem will NOT be checked, thus the hybrid ID (filesystem + device), to be on the very safe side. 2. Have udev helpers on hand that will fire fsck when filesystems listed on /etc/fstab are added for the first time (use (1) to detect unplug-replug). 3. enhance initscripts to mark in (1) anything we fsck syncrhonously. So we retain both behaviours, and fsck only once per boot (i.e. retain the semantics of the auto fsck). > We need to make the early boot system asynchronous too to avoid such > problems. It also affect USB disks and other busses with slow > discovery process. :( Correct. -- "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 _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
