When the iscsi target is pointed at an existing data file to serve via iscsi, it seems as though it rewrites all data in the file. This has been experienced on snv_69.
For instance... zfs snapshot pool/[EMAIL PROTECTED] zfs clone pool/[EMAIL PROTECTED] pool/ldom1-now iscsitadm create -b /pool/ldom1-now/root ldom1-now Notice that the disks in the zpool get hot and pool1/ldom1-now grows to roughly the size of the /pool/ldom1/root. It seems as though it is not destructive to the data, but the rewrite is annoying because: - The LUN won't come online until the rewrite is complete - I lose the sparseness of the clone Is there some reason that this is desirable? Is there a way to disable it? -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
