I realize I can't remove devices from a vdev, which, well, sucks and all, but I'm not going to complain about that. ;)
I have 4x500G disks in a RAIDZ. I'd like to repurpose one of them as I'm finding that all that space isn't really needed and that one disk would serve me much better elsewhere (as the second half of a mirror in a machine going into colo). SYS1 124G 1.21T 29.9K /SYS1 the only other storage in the machine is the small 60G pool made up of the remains of the OS disks, which is not going to be enough space to hold this all while I rebuild the array. Is there any way that I could possibly get one of the disks out of the pool long enough to be used as temp space while I rebuild the array with just 3 disks? I'm thinking either to pull it out of the machine and scribble all over it in another machine so that it no longer has its ZFS bits on it. If this plan works, then it would just be a blank disk (although it will have the same dev id, so I don't know if zfs will pick it back up anyway). The other plan is to replace it with a file that resides on the 60G partition. This seems more likely to work, but I don't know how that'd work out with the fact that the file would be a lot smaller than the actual pool. Maybe a thinly provisioned dev would do the trick, as I could then make it look like 500G, but it would only really use what it needed to resync the pool. Is this logic all correct based on how ZFS works on snv_64a? I could also upgrade first if that's at all recommended, it's something I've been meaning to do anyway. -brian -- "Perl can be fast and elegant as much as J2EE can be fast and elegant. In the hands of a skilled artisan, it can and does happen; it's just that most of the shit out there is built by people who'd be better suited to making sure that my burger is cooked thoroughly." -- Jonathan Patschke _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
