From owner-freebsd-questions@FreeBSD.ORG Tue Aug 12 20:14:59 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A77C7BB9 for ; Tue, 12 Aug 2014 20:14:59 +0000 (UTC) Received: from smtpy.mta.ca (smtpy.mta.ca [138.73.1.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B1782ACB for ; Tue, 12 Aug 2014 20:14:58 +0000 (UTC) Received: from qemg.mta.ca ([138.73.29.51]:49174 helo=qemg.org) by smtpy.mta.ca with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1XHIOM-0006HQ-NI; Tue, 12 Aug 2014 17:09:58 -0300 Date: Tue, 12 Aug 2014 17:14:56 -0300 (ADT) From: Andrew Hamilton-Wright To: Roland Smith Subject: Re: Problems with dump and restore In-Reply-To: Message-ID: References: <20140812193419.GB7166@slackbox.erewhon.home> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 20:14:59 -0000 Sorry, a bit of a follow up after some reading, as the soft-update bit was itching in my memory... On Tue, 12 Aug 2014, Roland Smith wrote: > In 2011, a problem was found with snapshots in combination with soft > updates *and* journaling (SU+J) hanging the machine. At that time the > recommendation was to switch off journaling. > According to https://wiki.freebsd.org/NewFAQs: > > If you want to use snapshot (dump -L) then disable the soft updates > journal for that filesystem. I have just realize that the soft update journal (newfs option -j enable) is actually not in play here, however "soft updates" (option -U) is. My understanding of the referenced bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160662 is that it is specifically referred to _journaled_ soft updates as being a danger, but soft updates using -U are not referred to by this bug. Is that your understanding as well? I believe that when I set up the filesystems for this machine in the first place, I specifically ensured that "-j disable" was chosen, for exactly this reason -- however my logbook does not contain enough detail for me to be sure. To be clear then, do I understand that your filesystem options include neither "-j enable" nor "-U"? Thanks, Andrew.