Date: Fri, 30 Aug 2013 13:37:10 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Charles Sprickman <spork@bway.net> Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: Boot problem if a ZFS log device is missing Message-ID: <522075D6.70600@FreeBSD.org> In-Reply-To: <CC82FB9B-0676-4391-A494-9B5C388C80B8@bway.net> References: <521F05F0.4090607@cloverinformatica.it> <521F0DEB.20408@FreeBSD.org> <CC82FB9B-0676-4391-A494-9B5C388C80B8@bway.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?522075D6.70600>