fsck in -current
Marc G. Fournier
scrappy at hub.org
Sat May 15 18:08:13 PDT 2004
I'm seriously considering putting 5.x onto my next server, to take
advantage of, if nothing else, the reduction in the GIANT LOCK reliance
... one "concern" I have is how fsck works in 5.x ...
Right now, on 4.x, I have an fsck running that has been going for ~3hrs
now:
# date; ps aux | grep fsck
Sat May 15 22:04:00 ADT 2004
root 40 99.0 4.5 185756 185796 p0 R+ 6:55PM 164:01.60 fsck -y /dev/da0s1h
and is in Phase 4 ...
In 5.x, if I'm not mistaken, fsck's are backgrounded on reboot, so that
the system comes up faster ... but:
a. wouldn't that slow down the fsck itself, since all the processes on the
machine would be using CPU/memory?
b. how long could fsck run in the background safely ... like, if I
rebooted a machine, fsck backgrounded and then all the processes
started up, is there a risk involved?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org Yahoo!: yscrappy ICQ: 7615664
More information about the freebsd-current
mailing list