> # zfs create pool raidz d1 … d8 Surely you didn't create the zfs pool on top of SVM metadevices? If so, that's not useful; the zfs pool should be on top of raw devices.
Also, because VxFS is extent based (if I understand correctly), not unlike how MVS manages disk space I might add, _it ought_ to blow the doors off of everything for sequential reads, and probably sequential writes too, depending on the write size. OTOH, if a lot of files are created and deleted, it needs to be defragmented (although I think it can do that automatically; but there's still at least some overhead while a defrag is running). Finally, don't forget complexity. VxVM+VxFS is quite capable, but it doesn't always recover from problems as gracefully as one might hope, and it can be a real bear to get untangled sometimes (not to mention moderately tedious just to set up). SVM, although not as capable as VxVM, is much easier IMO. And zfs on top of raw devices is about as easy as it gets. That may not matter _now_, when whoever sets these up is still around; but when their replacement has to troubleshoot or rebuild, it might help to have something that's as easy as possible. This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
