On Wed, 21 May 2008, Justin Vassallo wrote: > zpool add -f external c12t0d0p0 > zpool add -f external c13t0d0p0 (it wouldn't work without -f, and I believe > that's because the fs was online)
No, it had nothing to do with the pool being online. It was because a single disk was being added to a pool with raidz2. The error message that zpool would have displayed, without the -f, is something like: 'mismatched replication level'. By using the -f the files are now striping among three vdevs: the original raidz2, and each of the new disks. You are correct that the new disks now contain data that is at high risk. The disks cannot be removed from the pool. The best that can be done now is to attach mirrors to each of the disks. E.g.: # zpool attach external c12t0d0p0 c14t0d0p0 At least that way when a disk fails, you still have access to your data. The other option would be to create a new pool entirely with the five-disk raidz2 you originally wanted, and then do a zfs send | zfs recv for all datasets. Regards, markm _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
