OK ... the vmkernel.log on both machines :
2014-04-19T14:59:40.584Z cpu10:33258)LVM: 8349: Device eui.22cd000155a3fe57:1 detected to be a snapshot:
2014-04-19T14:59:40.584Z cpu10:33258)LVM: 8356: queried disk ID: <type 1, len 44, lun 0, devType 0, scsi 0, h(id) 10402944932408356314>
2014-04-19T14:59:40.584Z cpu10:33258)LVM: 8363: on-disk disk ID: <type 1, len 44, lun 0, devType 0, scsi 0, h(id) 15507285305951941117>
So I guess they are seeing it as a snapshot ... the LUN ID appears correct (eui.22cd000155a3fe57:1) on both machines,
The Device ID is the same on both machines (eui.22cd000155a3fe57) and formated as VMFS 5.60
I will try : esxcli storage vmfs snapshot mount -u <VMFS UUID> Ithe next time I reboot one of the servers...
Is there a "correct" procedure to remove the "snapshot" status from the drive?
From what i can see, the procedure is:
- Shutdown all Guests
- deregister the Guests
- Place both Servers in Maintenance mode
- unmount the iSCSI from both servers
- resignature the iSCSI using on server
- remount the iSCSI on both servers
- Remove both servers from maintenance mode.
- reregister the Guests
- power on all Guests
Am I right in assuming that performing a resignature is not destructive to data already on the drive, it's just changing the UUID of the drive ?
And therefor, in theory, the "queried disk ID" and the "on-disk disk ID" in the vmkernel.log output above would then be the same IDs ?
Thanks in advance.
@shley