On Sat, 2016-04-16 at 00:35 +0530, Ritesh Raj Sarraf wrote: > Hello Mike, > > All I can say is that I am able to see the behavior that you've mentioned (So > marking the bug as confirmed). THis is seen on my LIO iSCSI Setup running on 2 > Guest VMs. > > In doing that, I was surprised that those dev/mapper/ entries are now > symlinks. > My storage knowledge has rusted for some time now, but from what I recollect, > it > used to by direct block node names, not symlinks.
Maybe this could be of some help to you in debugging this further. Apr 16 00:34:11 debian-sanboot systemd[1]: Started Device-Mapper Multipath Device Controller. Apr 16 00:34:11 debian-sanboot systemd-udevd[949]: conflicting device node '/dev/mapper/sanroot' found, link to '/dev/dm-0' will not be created So I think my understanding was correct about Device Mapper's behavior. Now I'm not sure what 'systemd-udevd[949]' is reflecting here as. I doubt if that is the ID for the rules processing because then I'd have seen the respective rule. I hope this is of some use to you. My Debian time for today is running out :-) -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
