From owner-freebsd-stable@FreeBSD.ORG  Fri Aug 30 10:38:40 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@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 ESMTP id D87811FD;
 Fri, 30 Aug 2013 10:38:40 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id EFE2F2970;
 Fri, 30 Aug 2013 10:38:39 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA11720;
 Fri, 30 Aug 2013 13:38:33 +0300 (EEST)
 (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1VFM64-0007bu-PU; Fri, 30 Aug 2013 13:38:32 +0300
Message-ID: <522075D6.70600@FreeBSD.org>
Date: Fri, 30 Aug 2013 13:37:10 +0300
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130810 Thunderbird/17.0.8
MIME-Version: 1.0
To: Charles Sprickman <spork@bway.net>
Subject: Re: Boot problem if a ZFS log device is missing
References: <521F05F0.4090607@cloverinformatica.it>
 <521F0DEB.20408@FreeBSD.org> <CC82FB9B-0676-4391-A494-9B5C388C80B8@bway.net>
In-Reply-To: <CC82FB9B-0676-4391-A494-9B5C388C80B8@bway.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Maurizio Vairani <maurizio.vairani@cloverinformatica.it>,
 freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 10:38:40 -0000

on 30/08/2013 00:38 Charles Sprickman said the following:
> If one is willing to accept that data is lost (like the log device is totally smoked), is there a way to boot knowing that you may have some data loss, or is the only option to boot alternate media and force a pool import (assuming that works without the log device)?

I think it's the latter.  I am not aware of any way to select a behavior similar
to import -m or import -F during boot.
Perhaps... ZFS_IMPORT_MISSING_LOG should be a default behavior for a root pool
or maybe the behavior could be controllable by a tunable.

-- 
Andriy Gapon