From joseph@randomnetworks.com  Sun Jan 18 23:01:00 2004
Return-Path: <joseph@randomnetworks.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4096C16A4CE; Sun, 18 Jan 2004 23:01:00 -0800 (PST)
Received: from randomservers.com (randomservers.com [69.55.237.158])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B2B0443D41; Sun, 18 Jan 2004 23:00:57 -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 i0J6xwkP031045
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 18 Jan 2004 22:59:58 -0800 (PST)
	(envelope-from joseph@randomnetworks.com)
Received: from localhost (joseph@localhost)
	by randomservers.com (8.12.10/8.12.6/Submit) with ESMTP id i0J6xvpt031042;
	Sun, 18 Jan 2004 22:59:58 -0800 (PST)
	(envelope-from joseph@randomnetworks.com)
Message-Id: <20040118225309.C21889@randomservers>
Date: Sun, 18 Jan 2004 22:59:57 -0800 (PST)
From: Joseph Scott <joseph@randomnetworks.com>
To: Kirk McKusick <mckusick@beastie.mckusick.com>
Cc: mckusick@FreeBSD.org, David Gilbert <dgilbert@daveg.ca>,
	freebsd-gnats-submit@FreeBSD.org
In-Reply-To: <20040114160426.T12913@randomservers>
Subject: Re: FreeBSD 5.x filesystem snapshots, FreeBSD PR kern/58154 
References: <200401140729.i0E7Ttok003002@beastie.mckusick.com>
 <20040114160426.T12913@randomservers>

>Number:         61568
>Category:       kern
>Synopsis:       Re: FreeBSD 5.x filesystem snapshots, FreeBSD PR kern/58154
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    ceri
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jan 18 23:10:04 PST 2004
>Closed-Date:    Tue Jan 20 13:34:28 PST 2004
>Last-Modified:  Tue Jan 20 13:34:28 PST 2004
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 	The details I mentioned below appears to be about the same as the
 results in FreeBSD PR kern/58154.  I've CC'd the person who submitted that
 PR, perhaps he now as more details?
 
 	I've also tried this on a trial install of VMWare 4 on Windows XP.
 I was able to shutdown several times after a simple install.  Took several
 snapshots and now the shutdown just hangs.  The size of the fs doesn't
 appear to matter (size was mentioned in the PR).  So that makes 3
 different systems that showed the exact same results.
 
 	In order to add this additional info I've also CC'd this as a
 follow up to the PR.
 
 On Wed, 14 Jan 2004, Joseph Scott wrote:
 
 ->
 -> On Tue, 13 Jan 2004, Kirk McKusick wrote:
 ->
 -> -> Your results are exactly as I would expect. Each new snapshot
 -> -> needs to scan all the existing snapshots to purge them from
 -> -> its view (otherwise deleting older snapshots would cause them
 -> -> to be saved in the next older snapshot and you could never
 -> -> reclaim the space). The filesystem is not prevented from
 -> -> running while these purges are in progress, but the system
 -> -> will be slower because of the extra I/O.
 ->
 -> 	That makes sense.  On another snapshot note it appears that
 -> snapshots are causing problems under FreeBSD 5.2-RELEASE.  It took me
 -> awhile, but it looks like I can now repeat easily.
 ->
 -> 1.  Install FreeBSD 5.2-RELEASE from CD
 -> 2.  Run 'shutdown -h now' several times verifing that everything seems ok
 -> 3.  Snapshot a fs a couple of times (2 caused this to happen for me)
 -> 4.  Run 'shutdown -h now' and the system hangs at this line:
 ->
 -> syncing disks, buffers remaining...
 ->
 -> 5.  System requires a hard reset
 ->
 -> 	I've tried this now several times on two different systems with
 -> exactly the same results each time.  This was tested on right after
 -> completing an install of FreeBSD 5.2-RELEASE, the system was completely
 -> idle and not being used for anything else.  Even after rm'ing the snapshot
 -> files the shutdown would complete, but with errors which cause fsck's to
 -> be run when the system comes back up.
 ->
 -> 	This also seems to work with 'shutdown -r now', but it may require
 -> more than two snapshots to see the problem in that case.
 
 --
 Joseph Scott
 http://www.randomnetworks.com/joseph/blog/contact.php
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: ceri 
State-Changed-When: Tue Jan 20 13:33:54 PST 2004 
State-Changed-Why:  
Misfiled followup to kern/58154 [content migrated]. 


Responsible-Changed-From-To: gnats-admin->ceri 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Tue Jan 20 13:33:54 PST 2004 
Responsible-Changed-Why:  
Take from gnats-admin. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=61568 
>Unformatted:
