Hi, On Wednesday 22 February 2012 02:48:21 David Brodbeck wrote: > On Sat, Feb 18, 2012 at 9:26 PM, Erich Dollansky > <erichfreebsdl...@ovitrap.com> wrote: > > it will not even boot if there is only a single slice with root and the > > rest on it if the background fsck cannot be run. > > > > I have to go to real remote locations once in a while where an USP is not > > of real help anymore as the USP is not able to charge its battery before > > the next power failure comes. It happened there some times that the /usr > > slice needs a foreground check. Of course, all can be fixed. > > > > I cannot imagine that this would still work if / is on the same slice as > > the rest of the data. > > Why not? / gets mounted read-only, foreground fsck is run on /, system > boots... > > Maybe I'm just not understanding the problem here. I suppose in > theory your root filesystem could be so corrupt that it won't even > mount read-only, but I've never actually seen that happen except in > the case of an outright disk failure.
it happened to me under very strange circumstances. I was in a location with extremely bad power supply where even an USP has had problems recharging far enough to allow for a decent shutdown. I believe that main cause was that the last power failure occurred when fsck was running shortly after a reboot. As a result, only / got mounted. I have had to run a foreground fsck on the affected slices. It did not just happen once but several times. It did not happen to me since the switch to 6 many years ago. So, it is something rare, but it exists. Erich _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
