Thanks for your suggestions :) Another thing comes to my mind (expecially after a past bad experience with a buggy storage non-zfs backend). Usually (correct me if I'm wrong) the storage will be having redundancy on its zfs volumes (be it mirror or raidz). Once the redundant volume is exposed as a single iScsi volume, the virtual solaris will create his own zfs filesystem on it (unaware of its redundant backend). One of the "best practices" I've read specifically tells that single resource pools are unsafe. In this case, the backend knows it's actually redundant, but the virtual os does not, and actually have just a single resource mounted as its zfs disk. Is this situation safe? Should I expose two iScsi volumes and let the virtual os again use a redundant zpool on them? This would obviously double again the disk requirements...
Thanks again for any idea. Gabriele. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
