>> Note that "attach" has no option for -n which would just show me the >> damage I am about to do :-( > > In general, ZFS does a lot of checking before committing a change to the > configuration. We make sure that you don't do things like use disks > that are already in use, partitions aren't overlapping, etc. All of the > data integrity features in ZFS wouldn't be worth much if we allowed an > administrator to unintentionally destroy data.
which is why I am beginning to think of ZFS as the last filesystem I will need. But the head space transition is not easy for a guy that thrives on super stable technology. Like Solaris 8 :-) >> So I am making a best guess here that what I need is something like this : >> >> # zpool attach zfs0 c1t9d0 c0t9d0 >> >> which would mean that the fist disk in my zpool would be mirrored and >> nothing else. A weird config to be sure but .. is this what will happen? > > Yep, that's exactly what will happen. Lather, rinse, repeat for the > other disks in the pool, and you should be exactly where you want to be. Okay .. phasars on stun and in I go . >> I ask all this in painful boring detail because I have no way to backup >> this >> zpool other than tar to a DLT. The last thing I want to do is destroy my >> data when I am trying to add redundency. >> >> Any thoughts ? > > What you figured out is exactly the right thing. If you decide you want > to undo it, just use "zpool detach". > The only reason that I asked is that there is no explicit EXAMPLE in the manpage that says HOW TO UPGRADE FROM STRIPE TO MIRRORED STRIPES or maybe something that says RAID 0+1 or RAID 1+0. Just a bit more info in the ZFS manpages because that is the first place any admin will look. Not an online PDF file somewhere. Often times all I have to see what is going on in my server is s DEC VT220 terminal. Dennis _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss