cc'ing to storage-discuss where this topic also came up recently.
By default for most backing stores, COMSTAR will put its disk metadata
in the first 64K of the backing store as you say. So if you take a
backing store disk that is in use as an iscsitgt LUN and then run
"sbdadm create-lu /pa
The ZFS set shareiscsi=on mechanism is only used with the iscsitgt and
not with COMSTAR iscsi/target. Since you shifted to using
iscsi/target, it should not be working for you now.
Could it be that somehow you ended up with both kinds of target
(iscsitgt and comstar iscsi/target) running at
h the
customer's complaint that the change in state from "working" to "not
working" is taking too long seems pretty valid.
Peter
Neil Perrin wrote:
>
>
> Peter Cudhea wrote:
>> Your point is well taken that ZFS should not duplicate functionality
>> t
Your point is well taken that ZFS should not duplicate functionality
that is already or should be available at the device driver level.In
this case, I think it misses the point of what ZFS should be doing that
it is not.
ZFS does its own periodic commits to the disk, and it knows if those
