[linux-lvm] [BUG IN MS?]MS initiator reboots if lv+snapshot added as a lun

himanshu padmanabhi himanshu.padmanabhi at gmail.com
Thu Nov 13 09:53:22 UTC 2008


One IET target is having 2 luns as "Parent LV" and "its snapshot".

When MS initiator connects to it,it gets rebooted.

I came to know through forum that it is due to same disk signatures of the
two disks on initiator side.

If I attach "Parent LV" and "its snapshot" to different targets,then windows
initiator is behaving well.

But in Open-iSCSI initiator under linux,both cases work well,

*both parent lv and its snapshot are taking same IDs probably.How can i
change the id of snapshot.It determines ID internally through timestamps and
some other things.Both takes UUID obviously different.Windows might see
these either as two copies of the same volume or two paths to the same
volume, but their data diverges which causes Windows to freak out.Windows
stores a volume identifier in the MBR/GPT when a disk is first recognized
and uses that identifier for identification of storage volumes.But I cannot
make changes on client(initiator) side as my product is server machine.

basically *what changes should be made on the target side so that initiator
will recognize both as different disks?
Thanks and Regards,
Himanshu Padmanabhi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-lvm/attachments/20081113/e89b849b/attachment.htm>

More information about the linux-lvm mailing list