From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 16:04:12 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D56EE16A4CE; Mon, 16 Feb 2004 16:04:12 -0800 (PST) Received: from randomservers.com (randomservers.com [69.55.237.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id C501743D1D; Mon, 16 Feb 2004 16:04:12 -0800 (PST) (envelope-from joseph@randomnetworks.com) Received: from randomservers.com (randomservers [69.55.237.158]) by randomservers.com (8.12.10/8.12.6) with ESMTP id i1H02Hwn016774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Feb 2004 16:02:17 -0800 (PST) (envelope-from joseph@randomnetworks.com) X-Authentication-Warning: randomservers.com: Host randomservers [69.55.237.158] claimed to be randomservers.com Received: from localhost (joseph@localhost)i1H02H7m016766; Mon, 16 Feb 2004 16:02:17 -0800 (PST) (envelope-from joseph@randomnetworks.com) X-Authentication-Warning: randomservers.com: joseph owned process doing -bs Date: Mon, 16 Feb 2004 16:02:17 -0800 (PST) From: Joseph Scott X-X-Sender: joseph@randomservers To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, mckusick@freebsd.org, scottl@freebsd.org Message-ID: <20040216155005.J4957@randomservers> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=0.0 required=7.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on randomservers.com Subject: FreeBSD 5.2.1-RC2 fs snapshot problems. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 00:04:13 -0000 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. -- Joseph Scott http://www.randomnetworks.com/joseph/blog/contact.php