From night0wl@frost.ath.cx  Mon Feb 17 14:15:25 2003
Return-Path: <night0wl@frost.ath.cx>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3251837B401
	for <freebsd-gnats-submit@freebsd.org>; Mon, 17 Feb 2003 14:15:25 -0800 (PST)
Received: from frost.ath.cx (tm.213.143.79.46.dc.telemach.net [213.143.79.46])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EA29243FBD
	for <freebsd-gnats-submit@freebsd.org>; Mon, 17 Feb 2003 14:15:23 -0800 (PST)
	(envelope-from night0wl@frost.ath.cx)
Received: from localhost (localhost [127.0.0.1])
	by frost.ath.cx (ESMTP) with ESMTP id 9444D3EDC
	for <freebsd-gnats-submit@freebsd.org>; Mon, 17 Feb 2003 23:15:15 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by frost.ath.cx (ESMTP) with ESMTP id BB1A13ED9
	for <freebsd-gnats-submit@freebsd.org>; Mon, 17 Feb 2003 23:15:14 +0100 (CET)
Message-Id: <Pine.LNX.4.44.0302172314420.8234-100000@frost.lucky.si>
Date: Mon, 17 Feb 2003 23:15:14 +0100 (CET)
From: Night0wl <night0wl@frost.ath.cx>
To: freebsd-gnats-submit@freebsd.org
Subject: ufs2 snapshot code bugs

>Number:         48393
>Category:       kern
>Synopsis:       [ufs] ufs2 snapshot code bugs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    mckusick
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Feb 17 14:20:02 PST 2003
>Closed-Date:    Tue Aug 17 15:27:50 UTC 2010
>Last-Modified:  Tue Aug 17 15:27:50 UTC 2010
>Originator:     Night0wl <night0wl@frost.ath.cx>
>Release:        FreeBSD 5.0-RELEASE-p1 i386
>Organization:
Noviforum ltd.
>Environment:
 System: FreeBSD elfstone.noviforum.si 5.0-RELEASE-p1 FreeBSD 5.0-RELEASE-p1
 #0: Wed Feb 12 14:56:46 CET 2003 root@elfstone.noviforum.si:/export/system/usr.src/sys/i386/compile/UNIX i386
 
>Description:
 
 Hi There!UFS2 snapshot code bugs
 
  I am very sorry to inform you, that UFS2 snapshot code is very unstable
 on
 FreeBSD 5.x (-DPx, 5.0-RELEASE, 5.0-RELEASE-p1). mount -u -o snapshot
 works
 okay when filesystem is relatively empty, but you can crash the whole
 system
 if you have larger number of files stored on ufs partition.
 
  I tested this on 3 machines and and there is the same problem on all of
 them.
 
  You can crash machine using:
  1. mount -u -o snapshot
  2. dump -L
  3. mount uncleanly unmounted filesystem with background fsck enabled.
 
  Symptoms: machine works okay for about 30 seconds, then any I/O command
 hangs
 up (ls, cat, etc...).
 
  I produced this on a 850 GB (1.6 GB used) filesystem with 175263 files.
 
>How-To-Repeat:
 
>Fix:
  workarounds:
  1. don't create snapshots
  2. don't issue dump -L command (it creates filesystem snapshot)
  3. don't run background fsck
  4. add the following to your rc.conf:
  background_fsck="NO"
 
  This error does not accour with small number of files.
 
 This problem accours independetly on fact, that fs is mounted with
 softupdates
 or not.
 
 
 
 
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Mon Feb 17 14:30:39 PST 2003 
Responsible-Changed-Why:  
Reassign misfiled PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48393 
Responsible-Changed-From-To: freebsd-bugs->kirk 
Responsible-Changed-By: kris 
Responsible-Changed-When: Fri Oct 10 22:17:58 PDT 2003 
Responsible-Changed-Why:  
Assign to ufs2/snapshot maintainer 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48393 
Responsible-Changed-From-To: kirk->mckusick 
Responsible-Changed-By: kris 
Responsible-Changed-When: Sat Oct 11 01:06:07 PDT 2003 
Responsible-Changed-Why:  
Correct kirk's user id 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48393 

From: Cy Schubert <Cy.Schubert@komquats.com>
To: freebsd-gnats-submit@FreeBSD.org, night0wl@frost.ath.cx
Cc:  
Subject: Re: kern/48393: ufs2 snapshot code bugs
Date: Sat, 21 Feb 2004 21:50:58 -0800

 The size of the filesystem is not determining factor to tickle this bug. 
 I've experienced this bug on smaller filesystems, specifically /var on two 
 systems which are very actively writing data to /var through syslog.
 
 
 Cheers,
 --
 Cy Schubert <Cy.Schubert@komquats.com>        http://www.komquats.com/
 BC Government                     .                       FreeBSD UNIX
 Cy.Schubert@osg.gov.bc.ca         .                     cy@FreeBSD.org
 http://www.gov.bc.ca/             .            http://www.FreeBSD.org/
 
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: jh 
State-Changed-When: Thu Jul 15 10:22:05 UTC 2010 
State-Changed-Why:  
Is this still a problem for you? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48393 
State-Changed-From-To: feedback->closed 
State-Changed-By: jh 
State-Changed-When: Tue Aug 17 15:27:49 UTC 2010 
State-Changed-Why:  
Feedback timeout. 

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