[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2011-01-25 Thread Clint Byrum
Tagging hardy. Leaving off karmic as those will be sifted through and closed at EOL in 3 months, unlikely there would be an SRU at this point. ** Tags added: hardy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2011-01-25 Thread Clint Byrum
So, on inspecting this on hardy (I know the original report was against karmic), I have no /lib/udev/rules.d, and my /etc/udev/rules.d/65-dmsetup.rules looks like this: # This file causes devicemapper devices to be assigned names by udev # based on the name given to dmsetup. # See udev(8) for

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-05-08 Thread Jürgen Kreileder
Yep, no more messages about symlinks with lucid. I still do see some kind of race condition with lucid, though: May 8 16:24:53 sphere udevd-work[24973]: inotify_add_watch(6, /dev/dm-23, 10) failed: No such file or directory May 8 16:25:04 sphere udevd-work[24973]: inotify_add_watch(6,

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-05-06 Thread Wessel Dankers
Pasted from #444563, which actually does seem to be the same bug: I think I got it. In /lib/udev/rules.d/65-dmsetup.rules there's this line: ENV{DM_UUID}==LVM-*, PROGRAM=/bin/sh -c 'set `lvm lvdisplay -C -o vg_name,lv_name --noheadings /dev/$name` ; echo $1/$2', SYMLINK+=$result which is a

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-05-06 Thread Jürgen Kreileder
Good catch, will give it a try. Of course, /lib/udev/rules.d/65-dmsetup.rules isn't a conffile, so changes to it will be lost when the dmsetup package gets upgraded. (Also, this symlink rule isn't in lucid. On the other hand I didn't upgrade any of the machines showing this problem to lucid

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-05-06 Thread Wessel Dankers
You can create a file /etc/udev/rules.d/65-dmsetup.rules, which will override the file in /lib/udev/rules.d/. In lucid this seems to be handled completely differently (and much better imho): From /lib/udev/rules.d/56-lvm.rules: # Use DM name and split it up into its VG/LV/layer constituents.

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-04-06 Thread Jürgen Kreileder
** This bug is no longer a duplicate of bug 444563 rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-04-06 Thread Jürgen Kreileder
Removed the duplicate mark as I'm and others (see https://bugs.launchpad.net/ubuntu/+source/udev/+bug/444563/comments/32 for example) are pretty sure it's a different thing. -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-04-04 Thread teamnoir
*** This bug is a duplicate of bug 444563 *** https://bugs.launchpad.net/bugs/444563 I'm including a copy of the script I'm using to reproduce the problem. It assume you have a volume group named v4c of at least 8G available. ** Attachment added: script for reproducing a similar problem

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-04-02 Thread teamnoir
*** This bug is a duplicate of bug 444563 *** https://bugs.launchpad.net/bugs/444563 I'm seeing similar problems in a similar situation. I'm not doing backups but I am creating and removing a sequence of lv's and snapshots. Mine are on amd64 karmic. I don't believe I've seen these on lucid

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2010-04-02 Thread teamnoir
*** This bug is a duplicate of bug 444563 *** https://bugs.launchpad.net/bugs/444563 I'm not convinced this is the same bug either. Mine is more like yours than like #444563. -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2009-11-24 Thread Jürgen Kreileder
*** This bug is a duplicate of bug 444563 *** https://bugs.launchpad.net/bugs/444563 I'm not entirely convinced that is a duplicate too. Additionally to the messages already reported I also see upstart-udev-bridge restarting while creating the snapshots from time to time:

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2009-11-23 Thread ppww
*** This bug is a duplicate of bug 444563 *** https://bugs.launchpad.net/bugs/444563 Not convinced it's a duplicate of 444563, but perhaps related. I have a script that creates snapshots of / and /var in succession, and often receive the same strange error message the reporter notes above:

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2009-11-17 Thread Scott James Remnant
*** This bug is a duplicate of bug 444563 *** https://bugs.launchpad.net/bugs/444563 ** This bug has been marked a duplicate of bug 444563 rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link -- Race conditions when creating multiple LVM2 snapshots

[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots

2009-11-16 Thread Jürgen Kreileder
** Attachment added: btest.sh http://launchpadlibrarian.net/35763242/btest.sh ** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because