From owner-freebsd-current@FreeBSD.ORG Tue Jan 10 18:30:18 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACA62106566B; Tue, 10 Jan 2012 18:30:18 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (unknown [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452]) by mx1.freebsd.org (Postfix) with ESMTP id 863238FC15; Tue, 10 Jan 2012 18:30:18 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id q0AIUDP7062707; Tue, 10 Jan 2012 10:30:14 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201201101830.q0AIUDP7062707@chez.mckusick.com> To: Yamagi Burmeister In-reply-to: <20120109183051.1e4de3ca.lists@yamagi.org> Date: Tue, 10 Jan 2012 10:30:13 -0800 From: Kirk McKusick X-Spam-Status: No, score=0.0 required=5.0 tests=MISSING_MID, UNPARSEABLE_RELAY autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on chez.mckusick.com X-Mailman-Approved-At: Tue, 10 Jan 2012 18:33:54 +0000 Cc: freebsd-current@freebsd.org, bryce@bryce.net Subject: Re: FS hang when creating snapshots on a UFS SU+J setup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2012 18:30:18 -0000 > Date: Mon, 9 Jan 2012 18:30:51 +0100 > From: Yamagi Burmeister > To: jeff@freebsd.org, mckusick@freebsd.org > Cc: freebsd-current@freebsd.org, bryce@bryce.net > Subject: Re: FS hang when creating snapshots on a UFS SU+J setup > > Hello, > > I'm sorry to bother you, but you may not be aware of this thread and > this problem. We are several people experiencing deadlocks, kernel > panics and other problems when creating sanpshots on file systems > with SU+J. It would be nice to get some feedback, e.g. how can we > help debugging and / or fixing this problem. > > Thank you, > Yamagi First step in debugging is to find out if the problem is SU+J specific. To find out, turn off SU+J but leave SU. This change is done by running: umount tunefs -j disable mount cd rm .sujournal You may want to run `fsck -f' on the filesystem while you have it unmounted just to be sure that it is clean. Then run your snapshot request to see if it still fails. If it works, then we have narrowed the problem down to something related to SU+J. If it fails then we have a broader issue to deal with. If you wish to go back to using SU+J after the test, you can reenable SU+J by running: umount tunefs -j enable mount When responding to me, it is best to use my email as I tend to read it more regularly. Kirk McKusick