> > This should work. It shouldn't even lose the in-flight transactions. > ZFS reverts to using the main pool if a slog write fails or the > slog fills up.
So, the only way to lose transactions would be a crash or power loss, leaving outstanding transactions in the log, followed by the log device failing to start up on reboot? I assume that that would that be handled relatively cleanly (files have out of data data), as opposed to something nasty like the pool fails to start up. It's just data loss from zpool perspective. However it's data loss from application commited data. So applications that relied on commiting data for their own consistency might end up with a corrupted view of the world. NFS clients fall in this bin. Mirroring the NVRAM cards in the Separate Intent log seems like a very good idea. -r _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
