From owner-freebsd-stable@FreeBSD.ORG Fri Feb 3 10:15:38 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 286B9106564A for ; Fri, 3 Feb 2012 10:15:38 +0000 (UTC) (envelope-from adams-freebsd@ateamsystems.com) Received: from tali.ateamservers.com (tali.ateamservers.com [69.55.231.82]) by mx1.freebsd.org (Postfix) with ESMTP id EE4F68FC16 for ; Fri, 3 Feb 2012 10:15:37 +0000 (UTC) Received: from [192.168.15.220] (unknown [118.175.84.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tali.ateamservers.com (Postfix) with ESMTPSA id 2E28F12E9BE6; Fri, 3 Feb 2012 05:15:35 -0500 (EST) Message-ID: <4F2BB3CA.3060408@ateamsystems.com> Date: Fri, 03 Feb 2012 17:15:38 +0700 From: Adam Strohl Organization: A-Team Systems User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Marcel Bonnet References: <4F267B14.4060200@ateamsystems.com> <20120130120643.GA46785@icarus.home.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Ivan Voras 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: Fri, 03 Feb 2012 10:15:38 -0000 On 2/3/2012 15:45, Marcel Bonnet wrote: > Hi, what would be the best choice? > > 1. turn off SUJ and dump using -L flag and the turn it on again (but I'= m > affraid to destroy the system this way - is this possible?) Yes, this is what I have done for my 9.0 servers. Unfortunately you=20 need to be in single user mode if you need to change /'s setting. This = is because you cannot change this option while a file system is mounted=20 read+write. Rebooting into single user mode is the easiest way to do=20 this, as it leaves you with / mounted read only and everything else=20 dismounted for you. Then I ran: tunefs -j disable / For each volume that journaling was enabled for. As a side note remove the .sujournal file in the base of each volume=20 afterwards as it just takes up space. After doing this I have been using dump(8) nightly via cron(8) for about = a week now under 9.0 without issue. Running it on 11 servers currently. > 2. dump the unmounted partitions with a live cd, per example > > Sorry for top posting, mobile mail client problem. > > Em 30/01/2012 12:56, "Ivan Voras"escreveu: > > On 30/01/2012 13:06, Jeremy Chadwick wrote: > >>> For now I've turned off journaling (soft updates see... > It's a known bug: SU+J currently deadlocks when used with UFS snapshots= =2E > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://li... > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g"