From owner-freebsd-stable@FreeBSD.ORG Thu May 4 09:00:41 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 B2C8A16A400 for ; Thu, 4 May 2006 09:00:41 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CF6343D48 for ; Thu, 4 May 2006 09:00:41 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 320D046B03; Thu, 4 May 2006 05:00:40 -0400 (EDT) Date: Thu, 4 May 2006 10:00:40 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: David Kirchner In-Reply-To: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> Message-ID: <20060504095613.Y17611@fledge.watson.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org 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: Thu, 04 May 2006 09:00:41 -0000 On Wed, 3 May 2006, David Kirchner wrote: > However, one could argue that as quotas worked OK in releases prior to 6.0 > (and perhaps earlier), that there is a longer-term regression. In fact, it > seems that enabling snapshots by default appears to have caused a > significant regression for quotas and fsck operations (not for 'dump' > however, since the default is to not use them). The workaround is for the > user to disable all software that makes use of the feature, but the default > settings released to users leaves them enabled and thus implicitly > recommended.* > > I don't understand the need to issue a new release according to a strict > schedule if it means leaving critical bugs that affect a fundamental feature > of the OS: the filesystem itself. I think one would be well justified in > delaying a new release in order to fix a bug in a subsystem of this > magnitude. In fact, 6.1 contains significant stability improvements in the file system with respect to 6.0. It just happens to not yet fix all of the quota interactions with snapshots, even though it dos fix at least one serious one. You can take a look at the set of VFS, UFS, and soft updates fixes by searching for recent commits to RELENG_6 from Jeff Roberson. The quantity of significant performance and stability improvements in 6.1 with respect to 6.0 easily justifies cutting a release: while it may not correct every problem, it fixes a very large number. Robert N M Watson