on 30/08/2013 13:37 Andriy Gapon said the following:
> 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.
>
Maurizio,
you might want to try the following patch as an interim solution for your
environment:
--- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c
+++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c
@@ -4112,6 +4112,7 @@ spa_import_rootpool(const char *name)
}
spa->spa_is_root = B_TRUE;
spa->spa_import_flags = ZFS_IMPORT_VERBATIM;
+ spa->spa_import_flags |= ZFS_IMPORT_MISSING_LOG; /* XXX make tunable */
/*
* Build up a vdev tree based on the boot device's label config.
--
Andriy Gapon
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
