Hello??  Those that have committed to /sys in the past 1.5mo, awake?

I am continuing to suffer thru what appears to be inode deadlocks where
the resulting race-to-the-root soon locks everything up solid.  Tried to
figure out how to reproduce it on demand.  All I can characterize is the
file activity that FUBARs the system is in /tmp.

What ideas do people have to solve the problem?  crashdump are an
impossibility due to the locked up disk system.

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

Reply via email to