From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:59:08 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CE1E16A525 for ; Tue, 2 May 2006 17:59:08 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C4943D62 for ; Tue, 2 May 2006 17:59:00 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id F3A751A4DF1 for ; Tue, 2 May 2006 10:58:59 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6A31D5164F; Tue, 2 May 2006 13:58:59 -0400 (EDT) Date: Tue, 2 May 2006 13:58:59 -0400 From: Kris Kennaway To: stable@freebsd.org Message-ID: <20060502175859.GB91405@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NDin8bjvE/0mNLFQ" Content-Disposition: inline In-Reply-To: <20060502174429.GH753@dimma.mow.oilspace.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:59:08 -0000 --NDin8bjvE/0mNLFQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 02, 2006 at 09:44:29PM +0400, Dmitriy Kirhlarov wrote: > Hi! >=20 > On Tue, May 02, 2006 at 01:22:26PM -0400, Kris Kennaway wrote: > > > I think it's same problem as in thread "fsck_ufs locked in snaplk". > > > Is this problem fixed in fresh 6.1-PRE? > >=20 > > I think we've reproduced the problem, but it probably won't be fixed > > before the release. Sorry, the bug reports came too late in the > > release cycle. >=20 > Imho, it's bad idea -- create release with so important bug. It's not > coda, unionfs or something else. It's very useful. > I think, postpone release for fix this issue -- more fine. The release cycle has been in progress for over 3 months, and based on our understanding of the problems there is little chance of a quick fix for this issue even if the decision was made to delay the release further. Let me point out something important, which ties in to Scott's recent email. On February 21 -- that is over 2 months ago -- I sent email to this list containing a fix for the quota deadlocks that were known at the time. I got minimal response from users, but it was uniformly positive. The fix was committed, and the status of the "quota deadlocks" item on the 6.1-RELEASE todo list was changed from "must fix" to "believed fixed, please test". The next I heard about the problem was about a week ago when someone reported another deadlock and several others chimed in with "oh yeah, it still deadlocks for me too". Well, sorry folks, you should have told me in February. Or if you only found out about the problem a week ago, you need to recognize that problems raised at the last minute cannot always be fixed instantly. The best we can do now is provide a patch when the fix is available, and with the agreement of the release engineers it may be possible to commit the fix to the errata/security branch at a later date. In the meantime, the best advice is to avoid snapshots on busy systems (with or without quotas, they both can deadlock). Kris --NDin8bjvE/0mNLFQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEV53iWry0BWjoQKURAjKHAKCs9BMQe1Mej21lZWbbpZ2E58zT2QCfbMEW qpFsPlDUOf4BwDCsu/mOXfA= =2rfG -----END PGP SIGNATURE----- --NDin8bjvE/0mNLFQ--