[linux-lvm] Is cLVM necessary when accessing different logical volumes on a shared iSCSI target?

matthew patton pattonme at yahoo.com
Sat Jul 6 17:40:15 UTC 2013

> (either hard-coded or using tags) is *necessary* to make things working or if it 

> is just *adviseable* to prevent using a volume simultaneously from both clients?

You could probably make a case for saying it's adviseable but why do you want to play roulette with your data? Force it to do the right thing and you won't have to run the risk of it doing something unintended. Why the trepidation to doing it correctly?

> logical values are found by vgscan / lvscan, but I cannot access it. Is this the 
> expected behavior? Is there any chance (besides rebooting the client machine) to 
> recover from such a situation?

How did you disconnect from iSCSI? Did you gracefully log out of the client session? However you did it, it seems the kernel believes the device was just yanked offline and after repeated I/O failures marked it bad. Re-introducing the device doesn't magically clear the error state. Then again maybe it's as simple as you not bringing it fully online with a 'vgchange -ay <vg>' and an 'lvchange -ay <lv>'.

More information about the linux-lvm mailing list