WWID changes after Target reboot - Linux HA

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I was hoping somebody would be able to help with an issue that has me
stumped. Sorry if this has been asked before but I haven't found a
similar issue.

I have Corosync+Pacemaker serving up an iSCSI target, using
ocf::heartbeat:iSCSITarget and ocf::heartbeat:iSCSILogicalUnit. The
backstore is an iblock of an LVM LV stored in DRBD on a local drive
partition.

/dev/sda3 - DRBD physical partition
/dev/drbd0 - LVM PV
/dev/VG0/iscsi1 - LVM LV iblock for iSCSI

Every time that the target is removed and restored the WWID as seen by
the initiators changes (fetched with "/lib/udev/scsi_id -g -u -d
/dev/sdc"). I have multiple network routes so this changing of WWID
seriously upsets multipath.

For example, WWID is currently 36001405caa429dc7e474943bc6026541.
Previously it was 360014057b86b6a48432485fb4201da9d

Any pointers on how to make the WWID static?

Target servers and initiators are running Debian stable with backport
kernels.
linux-image-3.16.0-0.bpo.4-amd64 3.16.7-ckt2-1~bpo70+1
targetcli 2.0rc1-2
lio-utils 3.1+git2.fd0b34fd-2
python-rtslib 2.1-2

Frustratingly I have access to an almost identical setup where the WWID
is static. The only difference I can spot is that DRBD is on a separate
drive without a partition table.

Thank you,
Dan
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux