reassign 503268 lvm2 thanks On Mar 06, Chris Butler <chr...@debian.org> wrote:
> I'm also seeing this bug when removing snapshot LVs in my backup script, > although I'd be tempted to reassign it to lvm2. It looks like there's > actually a race going on between lvm and udev. If I stick sleeps in between > the lvremove calls, the problem doesn't appear. I think that subsequent > lvremove calls are getting the list of available LVs before udev has dealt > with the previous lvremove. It's then trying to access the LV device AFTER > udev has dealt with it, causing the error messages. I am not sure about what's happening, but I tend to agree that the problem is in LVM. -- ciao, Marco
signature.asc
Description: Digital signature
