From owner-freebsd-bugs@FreeBSD.ORG Wed Aug 23 10:48:18 2006 Return-Path: X-Original-To: freebsd-bugs@freebsd.org Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0210016A4F1; Wed, 23 Aug 2006 10:48:18 +0000 (UTC) (envelope-from sjr@comcast.net) Received: from alnrmhc11.comcast.net (alnrmhc13.comcast.net [206.18.177.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A18E43E52; Wed, 23 Aug 2006 10:45:55 +0000 (GMT) (envelope-from sjr@comcast.net) Received: from istari.comcast.net (c-69-139-159-113.hsd1.md.comcast.net[69.139.159.113](misconfigured sender)) by comcast.net (alnrmhc13) with ESMTP id <20060823104553b1300j7nhte>; Wed, 23 Aug 2006 10:45:54 +0000 Received: from istari.comcast.net (localhost [127.0.0.1]) by istari.comcast.net (8.13.6/8.13.6) with ESMTP id k7NAjjsp095772; Wed, 23 Aug 2006 06:45:49 -0400 (EDT) (envelope-from sjr@istari.comcast.net) Message-Id: <200608231045.k7NAjjsp095772@istari.comcast.net> Date: Wed, 23 Aug 2006 06:45:45 -0400 (EDT) From: "Stephen J. Roznowski" To: kib@FreeBSD.org In-Reply-To: <200608211721.k7LHLR1D047953@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-bugs@FreeBSD.org, sjr@comcast.net Subject: Re: kern/100365: snapshots on busy filesystem fail X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2006 10:48:18 -0000 On 21 Aug, Konstantin Belousov wrote: > Synopsis: snapshots on busy filesystem fail > > State-Changed-From-To: open->patched > State-Changed-By: kib > State-Changed-When: Mon Aug 21 17:06:17 UTC 2006 > State-Changed-Why: > The supposed fix for the problem was commited as rev. 1.128 > of the file sys/ufs/ffs/ffs_snapshot.c. Please, test and report results. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=100365 I've applied the fix by hand to 6.1-STABLE and the problem still appears to be there. dmesg still shows the same error. -- Stephen J. Roznowski (sjr@comcast.net)