From owner-freebsd-current@FreeBSD.ORG  Mon Feb 16 17:01:57 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8072016A4CE; Mon, 16 Feb 2004 17:01:57 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 53A8D43D1D; Mon, 16 Feb 2004 17:01:57 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i1H11k7E048190;
	Mon, 16 Feb 2004 17:01:50 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200402170101.i1H11k7E048190@gw.catspoiler.org>
Date: Mon, 16 Feb 2004 17:01:46 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: joseph@randomnetworks.com
In-Reply-To: <20040216155005.J4957@randomservers>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-fs@FreeBSD.org
cc: freebsd-current@FreeBSD.org
cc: scottl@FreeBSD.org
cc: mckusick@FreeBSD.org
Subject: Re: FreeBSD 5.2.1-RC2 fs snapshot problems.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2004 01:01:57 -0000

On 16 Feb, Joseph Scott wrote:
> 
> 	I just finished testing a fresh install of FreeBSD 5.2.1-RC2 and
> have verified that the problem mentioned in PR kern/58154 is still there.
> The problem is fairly simple to show:
> 
> 1.  Install a fresh 5.2.1-RC2 system.
> 2.  Shutdown a few times to show that it completes correctly.
> 3.  Create some snapshots of a filesystem (on 5.2.1-RC2 I did
>     3 snapshots of /usr).
> 4.  Try to shutdown again.
> 5.  Watch your system hang forever, unable to complete a shutdown
>     correctly.
> 
> 	I've done this samething on 3 different systems with the exact
> same results every single time.  If you cycle the power to reboot and then
> delete the snapshot files shutdown is able to work completely once more.
> 
> 	I'm more than willing to try out patches or different
> settings/options in an effort to try and track this down.  I would be
> thrilled to be able to use fs snapshots for systems at work, but as it
> stands not being able to shutdown a system makes the snapshot feature
> useless.
> 
> 	Sorry about cross posting this so much, but I've been trying to
> raise the attention level of this problem for weeks now without any luck.

I saw this as well a couple of months ago.  I think I was running
5.2-CURRENT.