On Friday, December 6, 2002, at 01:39 PM, Archie Cobbs wrote:

Kirk McKusick wrote:
Does the background fsck process continue to run, or does the whole
system come to a halt? If the fsck process continues to run, what
happens when it eventually finishes? Is the system still dead, or
does it come back to life? If the system does not come back to life
can you get me the output of `ps axl'? If not, can you break into
the debugger and get a ps output? (You will need to have the DDB
option specified in your config file).
OK, here is some more info..

I easily reproduced the problem again. So far it's 100% reproducible.
This time to reproduce it simply booted in single user mode, typed
"mount -a -t nonfs" and then pulled the plug.

After the reboot, the HDD light soon stops blinking altogether. I
waited for several minutes (which should have been long enough) and
it never came back to life, which is not surprising considering
there's no disk activity.

Breaking into the debugger still works. However, pressing the soft
power button no longer causes a graceful shutdown as it normally does.

To copy the 'ps' debugger output, I'd have to manually copy it all,
so here are just a few highlights:

Proc		State
----		-----
fsck_ufs	0004000 norm[SLPQ nbufbs c036e5b0][SLP]
fsck		0004002 norm[SLPQ   wait c124dce8][SLP]
syncer		0000204 norm[SLPQ nbufbs c036e5b0][SLP]
vnlru		0000204 norm[SLPQ vlruwt c12c0ce8][SLP]
bufdaemon	0000204 norm[SLPQ qsleep c036e5a4][SLP]
swapper		0000200 norm[SLPQ  sched c0315a20][SLP]

Softupdates is enabled on /usr and /var but not /.

This machine also acts as an NFS client for /home/archie.

Why does softupdates not get enabled on / , by default on the install?

-DR


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to