https://bugzilla.novell.com/show_bug.cgi?id=242047 jimc@math.ucla.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jimc@math.ucla.edu | ------- Comment #5 from jimc@math.ucla.edu 2007-03-06 12:12 MST ------- @Werner: As the author of a lot of the boot scripts you speak from experience here. Starting in SuSE 9.3 or 10.0 fsck appeared in the initrd (and I put my forcefsck hack in as well). But unfortunately the initrd can't know whether the /forcefsck file exists until after it has run fsck and then mounted the root, so the root wouldn't get a full fsck until its timeout or mount count expires, except on my system where I can use my command line arg. Some sysops think it's important to forcefsck on a regular schedule, to avoid a random long delay in booting, which of course would only happen when a customer particularly wants service fast. Here's a compromise: initrd does a nonforced fsck and mounts the root. Then it checks for /forcefsck [jimc says: also checks for commandline forcefsck arg] and if found, it UNmounts the root, runs fsck -f, and remounts. However, other sysops either use only builtin drivers in the stock kernel or they compile their own kernel with their favorite drivers hardwired; this is out of security paranoia, for the ones whose postings I've read. Then no initrd would be necessary or desired, and that means /etc/init.d/boot.rootfsck still has to exist (and be sensitive to /forcefsck). It's kind of a fragile kludge to make a rule that when boot.rootfsck runs, the root has to be remountable readonly, but not too much occurs ahead of it, and I don't see any better solution. Of course the *real* solution for this problem is if /sbin/udevsettle actually worked. It exits when there are no queued hotplug events waiting for udev to execute them; it *should* exit when the last event has been completely finished, not when it is started. Re. your comment on fuser: on my work systems (125 boxes running SuSE 10.1) we often have the problem of fuser getting stuck when there's a stale NFS mount. So we do a timeout thing: do the fuser step in a subshell in the background in parallel with a "sleep", and whichever finishes first, murder the other. (This is in admin cleanup scripts, not for booting.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.