>>>>> "re" == Richard Elling <richard.ell...@gmail.com> writes:
re> in the case of a properly exported pool, we should be allowed
re> to import sans slog.
seems so, but the non properly exported case is still important. for
example NFS HA clusters would stop working if slogs were always
ignored on import---you have to 'import -f' and roll the slog like
it does now.
And I think the desire for the removal feature is both these:
* don't want to lose whole pool if slog goes bad
* want to test out slog, then remove it. or replace with smaller
slog.
so your case handles the second (though you'd have to export/import to
remove, while you can add online)
but it does not handle the first.
I want to make sure the common conception of the scope of the slog
user-whining doesn't ``creep'' narrower. I think the original slog
work included a comment like:
q. shouldn't we be able to remove them?
a. yes that would be extremely easy to do, but my deadline is
already tight so I want to resist scope creep.
now, here we are, a year later...
pgphOsHs7FAhV.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
