From owner-freebsd-stable@FreeBSD.ORG Mon Jan 30 14:55:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 626C81065675 for ; Mon, 30 Jan 2012 14:55:08 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0EE738FC12 for ; Mon, 30 Jan 2012 14:55:07 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1RrsOp-0008QY-Kj for freebsd-stable@freebsd.org; Mon, 30 Jan 2012 15:40:03 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Jan 2012 15:40:03 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Jan 2012 15:40:03 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 30 Jan 2012 15:38:05 +0100 Lines: 18 Message-ID: References: <4F267B14.4060200@ateamsystems.com> <20120130120643.GA46785@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120110 Thunderbird/9.0 In-Reply-To: <20120130120643.GA46785@icarus.home.lan> Subject: Re: FreeBSD 9 crash/deadlock when dump(8)ing file system with journaling enabled. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2012 14:55:08 -0000 On 30/01/2012 13:06, Jeremy Chadwick wrote: >> For now I've turned off journaling (soft updates seem fine) and that >> works around the issue. >> >> Let me know if I can provide more details etc! > > I'm not sure, but this may be an after-effect of known problems right > now with SU+J on 9.0. It would help if you could state if you're using > "dump -L" or not. > > I've seen the "deadlock" behaviour you describe on older FreeBSD > versions (dating back to at least 7.x) when using "dump -L", which > generates a fs snapshot. Obviously 7.x does not have SU+J, so I'm a > little surprised disabling journalling fixes the problem for you. It's a known bug: SU+J currently deadlocks when used with UFS snapshots.