Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Nov 2005 21:23:10 -0600 (CST)
From:      Greg Rivers <gcr+freebsd-stable@tharned.org>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Recurring problem: processes block accessing UFS file system
Message-ID:  <20051121205535.W32523@nc8000.tharned.org>
In-Reply-To: <20051122021224.GA12402@xor.obsecurity.org>
References:  <20051121164139.T48994@w10.sac.fedex.com> <20051122021224.GA12402@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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.


> fsck -B also uses them, but shouldn't be running except at boot time.
>

Right, it isn't even at boot since I have background_fsck disabled.


> You should take this up with Kirk McKusick <freebsd@McKusick.COM> - in 
> the meantime you can work around it by not making use of UFS snapshots.
>

Sounds good.  Even though the problem may not be snapshot related, it 
certainly seems to be UFS related.  Thanks for your suggestions and your 
prompt reply.

-- 
Greg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051121205535.W32523>