This makes sense for the most part (and yes, I think it should be done by the file system, not a manual grovelling through vdev labels).
The one difference I would make is that it should not fail if the pool _requires_ a scrub (but yes, if a scrub is in progress...). I worry about this requirement, as my pool has had errors since the second SATA drive was attached (admitedly, it was clean as I detached the EIDE drive). If a scrub cannot clean up the errors on the (bad) disk, the inability to cleanly detach the good disk in a mirror and import the pool from that disk on another system leaves you in the same limbo that I am in now. Thus, fail on the normal attempt, but allow a force if the scrub or resilver are finished but you still have errors on what would be the last (disk) mirror on the system. This would also provide a way to offline a fixed file system state. That is, dettach the mirror, power down, and pull the disk. Some time later, put the disk into a system and pull in the pool(s), creating a data pool of a known, clean state, with known files. One could think of this as a special case of the export function, where one only exports one side of a mirrored pool.. Rainer This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
