Date: Thu, 29 Aug 2013 17:38:06 -0400 From: Charles Sprickman <spork@bway.net> To: Andriy Gapon <avg@freebsd.org> Cc: Maurizio Vairani <maurizio.vairani@cloverinformatica.it>, freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: Boot problem if a ZFS log device is missing Message-ID: <CC82FB9B-0676-4391-A494-9B5C388C80B8@bway.net> In-Reply-To: <521F0DEB.20408@FreeBSD.org> References: <521F05F0.4090607@cloverinformatica.it> <521F0DEB.20408@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 29, 2013, at 5:01 AM, Andriy Gapon wrote: > on 29/08/2013 11:27 Maurizio Vairani said the following: >>=20 >> I am able to boot the PC without a cache device but not without a log = device. Why ? >=20 > The log could potentially contain uncommitted entries. Without the = log device > there is no knowing if it did or did not. And if it did then the pool = is > inconsistent state without the log device and so it can not be = imported. 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)? Charles >=20 > The cache is not persistent and so there is nothing needed from it = upon a boot. >=20 > --=20 > Andriy Gapon > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC82FB9B-0676-4391-A494-9B5C388C80B8>