Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Jan 2003 10:42:39 -0500 (EST)
From:      Roy Hooper <rhooper@slinky.toybox.ca>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   kern/47105: large filesystems may cause infinite panic loop
Message-ID:  <200301151542.h0FFgdjI003057@slinky.toybox.ca>

next in thread | raw e-mail | index | archive | help

>Number:         47105
>Category:       kern
>Synopsis:       large filesystems may cause infinite panic loop
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 15 07:50:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Roy Hooper
>Release:        FreeBSD 5.0-RC i386
>Organization:
>Environment:
System: FreeBSD slinky.toybox.ca 5.0-RC FreeBSD 5.0-RC #2: Thu Jan 9 14:47:14 EST 2003 root@slinky.toybox.ca:/usr/src/sys/i386/compile/TOYBOX2 i386

Filesystem  1K-blocks     Used    Avail Capacity iused    ifree %iused  Mounted on
/dev/ad0s1a    128990   117532     1140    99%    3587    12667   22%   /
devfs               1        1        0   100%       0        0  100%   /dev
/dev/ad0s1f    257998     8318   229042     4%      37    32473    0%   /tmp
/dev/ad0s1g  12777510  7267820  4487490    62%  396091  1207491   25%   /usr
/dev/ad0s1e    257998    65068   172292    27%    4428    28082   14%   /var
procfs              4        4        0   100%       1        0  100%   /proc
/dev/ad2s1a 115396956 40978004 65187196    39%  915926 13509672    6%   /backup


>Description:
	After creating a snapshot with 'mount -u -o snapshot /backup/snapshots/snap1 /backup', and running ls on the directory, both the mount and ls hung and were in "D" state in ps.  Issuing a reboot request failed -- the system stayed up -- as did ctrl-alt-delete.  I had to resort to a poweroff.  When the system came back up, the background fsck began and the system came up.  Eventually the system paniced and rebooted, but came back up.  After the 2nd panic during background fsck, the system stopped rebooting and needed a manual fsck to repair the disk.
	This is slightly different than my experience with RC2 where making a snapshot on the same large filesystem would cause a panick and reboot, as opposed to a hang.

	I have never successfully had the large filesystem (/dev/ad2s1a) finish a snapshot -- the mount process is always hung.  The background fsck also never exits (it always eventually panics).

	Unfortunately the machine is headless, so I missed the panic messages.

>How-To-Repeat:
	create a snapshot on a large filesystem.
>Fix:
	Don't use snapshots and set background_fsck="NO" in /etc/rc.conf	

>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301151542.h0FFgdjI003057>