-
copecAre there any issues with exporting a whole disk through comstar iscsi or anything special I need to do? I'm trying export all the disks of a zpool with some encrypted datasets so I can access them
-
copecThe initiator machine sees the proper lun size, but isn't seeing anything on the disks
-
copecThe zpool isn't imported on the target machine
-
copec(I've never used physical disks before, only zvols)
-
tsoomecopec you had some data on those disks?
-
copectsoome: yeah. I converted a machine to omnios from linux, but it can’t mount some encrypted zfs datasets. I only need some specific things off them so I figured I would try this.
-
tsoomethen you need to specify separate storage for lun metadata
-
gitomat[illumos-gate] 15307 zpool status -v list wrong devicename after 15232 -- Marco van Wieringen <marco.van.wieringen⊙pen>
-
copectsoome: Is that meta=path when adding the lun? ( illumos.org/man/8/stmfadm )
-
copecAh, "Logical units registered with the STMF require space for the metadata to be stored. When a zvol is specified as the backing store device, the default will be to use a special property of the zvol to contain the metadata. For all other devices, the default behavior will be to use the first 64k of the device. An alternative approach would be to use the meta property in a create-lu subcommand to specify an alternate file to contain the metadata.
-
copecIt is advisable to use a file that can provide sufficient storage of the logical unit metadata, preferably 64k."