Boot problem if a ZFS log device is missing
Andriy Gapon
avg at FreeBSD.org
Fri Aug 30 10:38:40 UTC 2013
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
More information about the freebsd-stable
mailing list