You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find that the device mapper will try about 5 times when ioctl meet EBUSY errors, but it still fails in my scenario. When it fails, I monitor which process preventing it from delete the thin device, via the lsof tool. I find that a process named (udev-worker) holds reference to the thin device.
I am not familiar with udev (systemd-udevd), I guess the DM_DEV_REMOVE_CMD ioctl triggers the udev to handle events like "remove" events? But I am not sure that will udev receive and process any event before the ioctl has actually succeed (the DM_DEV_REMOVE_CMD failed with EBUSY and the thin device has not been deleted).
Activity