Recurring problem: processes block accessing UFS file system
kris at obsecurity.org
Tue Nov 22 04:39:54 GMT 2005
On Mon, Nov 21, 2005 at 09:23:10PM -0600, Greg Rivers wrote:
> On Mon, 21 Nov 2005, Kris Kennaway wrote:
> >Looks like a UFS snapshot deadlock. Are you running something like dump
> >-L on this filesystem, or making other use of snapshots?
> Indeed I am (dump -L), but as I said (not very clearly, sorry), the
> deadlock also occurs under normal operation when no snapshots are running
> or have ever been run since boot. It's just much less frequent in this
> case. Disabling dumps altogether was one of the first things I tried.
It may not be the same problem. You should also try to obtain a trace
when snapshots are not implicated.
'show lockedvnods' is very important for diagnosing filesystem
deadlocks, and 'alltrace' is the easiest way to obtain stack traces
for the resulting processes that are holding locks. You'll want to
'set $lines=0' and capture the output from the serial console to a
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051121/69d59a5b/attachment.bin
More information about the freebsd-stable