On Mon, Jun 29, 2015 at 03:46:04PM +0200, Hannes Reinecke wrote: > So apparently you can only set the cookie for DM_DEVICE_RESUME, > _not_ DM_DEVICE_RELOAD. There are various alternative modes of operation to choose between. It is essential to pick one and use it consistently alongside the corresponding udev rules. These sorts of problems arise when switching between different modes, whether deliberately or otherwise. > Which is odd, as DM_DEVICE_RELOAD is the only call I'll ever do; > apparently it's being translated internally into a > suspend/reload/resume cycle. I didn't think that one got translated internally. Please point to the actual source code that's causing the problems, and say which versions of the udev rules (and libdevmapper and kernel driver) were installed when getting the errors. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
