[Bug 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container
The message is warning you that whatever process launched 'vgs' leaked a file descriptor i.e. it has granted 'vgs' access to a file that should not be there. So you'll want to move this bug to whichever component that is e.g. something related to 'lxc' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871487 Title: anon_inode:[eventfd] leaked on vgs invocation inside lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1256905] Re: lvcreate fails with 'mlock failed' on armhf
Try this from 2.02.99: https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-November/000391.html Alasdair ~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256905 Title: lvcreate fails with 'mlock failed' on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1256905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 360237] Re: cannot boot root on lvm2 with (largish) snapshot
*** This bug is a duplicate of bug 995645 *** https://bugs.launchpad.net/bugs/995645 On Fri, Apr 11, 2014 at 06:55:15PM -, Seth wrote: I'd like to have the record show that this bug is ancient so we can measure the level of neglect. Snapshot loading got speeded up in upstream kernel 3.14. Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/360237 Title: cannot boot root on lvm2 with (largish) snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/360237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1083680] Re: lvm man pages are confusing when it comes to units
Output is configurable as described. Input always uses 512 or 1024 as most people would expect: I rejected patches to change this upstream when this last came up for discussion several years ago for multiple reasons amply covered in the ubuntu wiki URL and comments you linked to. Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083680 Title: lvm man pages are confusing when it comes to units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1083680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1075950] Re: Starting clustered lvm vg pool fails with status 5
On Sat, Jan 12, 2013 at 12:03:16AM -, Dmitrijs Ledkovs wrote: Debian dropped clustered lvm2 support. * Drop cluster (clvm) support. It never properly worked and is more dead than alive. -- Bastian Blank wa...@debian.org Wed, 02 Jan 2013 11:11:41 +0100 It it certainly not dead upstream and does work properly. It remains supported in Fedora/Red Hat Enterprise Linux/CentOS and presumably in many other distributions too. Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075950 Title: Starting clustered lvm vg pool fails with status 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1075950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
On Sat, Jan 12, 2013 at 12:03:21AM -, Dmitrijs Ledkovs wrote: Debian dropped clustered lvm2 support. * Drop cluster (clvm) support. It never properly worked and is more dead than alive. -- Bastian Blank wa...@debian.org Wed, 02 Jan 2013 11:11:41 +0100 Do we still want it in Ubuntu? It it certainly not dead upstream and does work properly. It remains supported in Fedora/Red Hat Enterprise Linux/CentOS and presumably in many other distributions too. Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833368 Title: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1096847] [NEW] quantal: pvmove on/from SSD corrupts data
*** This bug is a duplicate of bug 1082325 *** https://bugs.launchpad.net/bugs/1082325 You don't give the lvm version, but it sounds like you might be missing the patch for https://bugzilla.redhat.com/832392 . Aladsair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096847 Title: quantal: pvmove on/from SSD corrupts data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1096847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
I think we removed that 'incompatible' message upstream earlier this year, so you might want to look at a more recent upstream version. Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833368 Title: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
On Thu, Nov 22, 2012 at 05:10:25PM -, Robert McGrath wrote: The spelling fixes are also still in place, I notified upstream: https://github.com/beekhof/pacemaker/commit/932e41e Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833368 Title: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 585027] Re: Race condition with dmsetup causes 'map already present' messages
I don't follow this. Your title mentions 'dmsetup' but your description only talks about multipathd. What is the problem here? One of the multipath commands in your loop failing to wait until the associated udev action has completed before exiting? Or some dmsetup command you are running in parallel that interferes? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/585027 Title: Race condition with dmsetup causes 'map already present' messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/585027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 585027] Re: Race condition with dmsetup causes 'map already present' messages
On Mon, Jul 09, 2012 at 03:29:11PM -, Peter Petrakis wrote: In examining the ioctl interface to device mapper (kernel), I have not found any architecture that assures that when a device mapper device has been marked for deletion, that this information is relayed back to userspace so it can block on this deletion. An example will clarify things. If this is the same process that issued the deletion that needs to wait till the device has gone, then the udevcookie mechanism is meant to provide that already. (Multipathd is supposed to be using that mechanism, upstream at least.) If it's a different process, then I consider it's userspace's job to co-ordinate the sequencing of ioctls that conflict with each other. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/585027 Title: Race condition with dmsetup causes 'map already present' messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/585027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 585027] Re: Race condition with dmsetup causes 'map already present' messages
On Mon, Jul 09, 2012 at 04:33:25PM -, Peter Petrakis wrote: I'm not familiar with the cookie feature you mentioned, but we appear to have some of the capability here. I haven't compared it to upstream yet. The code issuing the removal ioctl specfies a cookie (a semaphore with a positive value). It then waits until the semaphore drops to 0. The last thing the udev rules do after they've updated /dev is decrement the semaphore, which wakes up the original code. There are libdevmapper calls and dmsetup commands to update/query cookie state. udev 'watch' rules can run out-of-band and need careful configuration to avoid problems. If libvirt is issuing dm ioctls or dmsetup commands itself then it might also need to be udevcookie-aware - not something that's arisen in any discussions yet - there is some default udevcookie handling built into dmsetup commands. I was assured the upstream multipath udevcookie support was complete, but I've not verified that personally - perhaps we have a situation that's overlooked here. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/585027 Title: Race condition with dmsetup causes 'map already present' messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/585027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 585027] Re: Race condition with dmsetup causes 'map already present' messages
I don't follow this. Your title mentions 'dmsetup' but your description only talks about multipathd. What is the problem here? One of the multipath commands in your loop failing to wait until the associated udev action has completed before exiting? Or some dmsetup command you are running in parallel that interferes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/585027 Title: Race condition with dmsetup causes 'map already present' messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/585027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 585027] Re: Race condition with dmsetup causes 'map already present' messages
On Mon, Jul 09, 2012 at 03:29:11PM -, Peter Petrakis wrote: In examining the ioctl interface to device mapper (kernel), I have not found any architecture that assures that when a device mapper device has been marked for deletion, that this information is relayed back to userspace so it can block on this deletion. An example will clarify things. If this is the same process that issued the deletion that needs to wait till the device has gone, then the udevcookie mechanism is meant to provide that already. (Multipathd is supposed to be using that mechanism, upstream at least.) If it's a different process, then I consider it's userspace's job to co-ordinate the sequencing of ioctls that conflict with each other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/585027 Title: Race condition with dmsetup causes 'map already present' messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/585027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 585027] Re: Race condition with dmsetup causes 'map already present' messages
On Mon, Jul 09, 2012 at 04:33:25PM -, Peter Petrakis wrote: I'm not familiar with the cookie feature you mentioned, but we appear to have some of the capability here. I haven't compared it to upstream yet. The code issuing the removal ioctl specfies a cookie (a semaphore with a positive value). It then waits until the semaphore drops to 0. The last thing the udev rules do after they've updated /dev is decrement the semaphore, which wakes up the original code. There are libdevmapper calls and dmsetup commands to update/query cookie state. udev 'watch' rules can run out-of-band and need careful configuration to avoid problems. If libvirt is issuing dm ioctls or dmsetup commands itself then it might also need to be udevcookie-aware - not something that's arisen in any discussions yet - there is some default udevcookie handling built into dmsetup commands. I was assured the upstream multipath udevcookie support was complete, but I've not verified that personally - perhaps we have a situation that's overlooked here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/585027 Title: Race condition with dmsetup causes 'map already present' messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/585027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
This code has since changed upstream. Start here http://git.fedorahosted.org/git/?p=lvm2.git;a=commit;h=d81498a824e66acca994807643e9df1e452fd61c (dependencies on earlier commits I think too) Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833368 Title: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 360237] Re: cannot boot root on lvm2 with (largish) snapshot
Persistent on disk, but cached completely in memory by reading the entire COW device when activating it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/360237 Title: cannot boot root on lvm2 with (largish) snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/360237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 360237] Re: cannot boot root on lvm2 with (largish) snapshot
Metadata (not data) is cached i.e. the block mappings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/360237 Title: cannot boot root on lvm2 with (largish) snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/360237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 726677] Re: [Wishlist] Upgrade lvm2 to at least 2.02.73
On Mon, Oct 17, 2011 at 11:45:53PM -, Steve Langasek wrote: Alasdair, is 2.02.86 also safe these days, or should we be holding back on 2.02.84? Debian has updated to 2.02.86 since this bug was filed. 2.02.86 should be OK, but patch it at least with the patch for: Terminate pv_attr field correctly. (Otherwise 'pvs' can segfault when running.) For the next RHEL5 and RHEL6 releases, we're using 2.02.88 and backporting selected changes to it as the current upstream repo has some significant development work going on in it and it'll be several more weeks before there's another release. Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726677 Title: [Wishlist] Upgrade lvm2 to at least 2.02.73 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/726677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 836329] Re: lvm volumes not listed if lvm has command_names option = 1
On Wed, Sep 07, 2011 at 03:28:45PM -, Serge Hallyn wrote: I think this would be legitimate as a bug against lvm for spitting out the command_name prefix when --noheadings is specified. --noheadings only refers only to the headings line. command_names applies to all output lines. The option exists because LVM1 output used to look like that and this option was to try to ease the transition to LVM2. Alasdair -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/836329 Title: lvm volumes not listed if lvm has command_names option = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/836329/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 836329] Re: lvm volumes not listed if lvm has command_names option = 1
On Wed, Sep 07, 2011 at 03:28:45PM -, Serge Hallyn wrote: I think this would be legitimate as a bug against lvm for spitting out the command_name prefix when --noheadings is specified. --noheadings only refers only to the headings line. command_names applies to all output lines. The option exists because LVM1 output used to look like that and this option was to try to ease the transition to LVM2. Alasdair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/836329 Title: lvm volumes not listed if lvm has command_names option = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/836329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 796199] [NEW] pvscan report wrong size
Fixed upstream in 2.02.65. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796199 Title: pvscan report wrong size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/796199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489398] Re: Unable to use use LVM with DRBD block devices as PV
Dealt with upstream a while back. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in ubuntu. https://bugs.launchpad.net/bugs/489398 Title: Unable to use use LVM with DRBD block devices as PV -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 726677] Re: [Wishlist] Upgrade lvm2 to at least 2.02.73
I'm not recommending upgrades to anything other than 2.02.84 at the moment, due to other issues. So far I regard 2.02.84 as 'stable'. (Add 'Fix to make resuming exclusive cluster mirror use local target type.' to the release if you want.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726677 Title: [Wishlist] Upgrade lvm2 to at least 2.02.73 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 593228] Re: Misleading error message with pvremove
Change message upstream: http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/tools/pvremove.c.diff?r1=1.32r2=1.33cvsroot=lvm2f=h -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/593228 Title: Misleading error message with pvremove -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274264] Re: lvcreate --type undocumented
--type is now in the lvcreate man page upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/274264 Title: lvcreate --type undocumented -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174032] Re: lvresize fails attempting to call fsadm with --resizefs parameter
We did actually get --resizefs and fsadm working upstream (most of the time). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/174032 Title: lvresize fails attempting to call fsadm with --resizefs parameter -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489398] Re: Unable to use use LVM with DRBD block devices as PV
Dealt with upstream a while back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/489398 Title: Unable to use use LVM with DRBD block devices as PV -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658144] Re: LVM2 - flock failed: Interrupted system call
flock failed happens if you interrupt (e.g. by pressing control C) an lvm command that is waiting to obtain a lock. Commands hanging can be caused by races, sometimes involving asynchronous commands issued by udev. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658144 Title: LVM2 - flock failed: Interrupted system call -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658144] Re: LVM2 - flock failed: Interrupted system call
So when it hangs, you need to see what else is running/hanging on the machine, whether some other process holds the file locks etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658144 Title: LVM2 - flock failed: Interrupted system call -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 612310] Re: dmsetup rename sometimes creates new device name but does not remove original device name
Might be udev-rule-related. See if works OK with current upstream, or in an independent (i.e. not Debian-based) distribution with up-to-date packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/612310 Title: dmsetup rename sometimes creates new device name but does not remove original device name -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719333] Re: CLVM not locking LV's properly even when set to exclusive
And further upstream fixes since allow snapshots to be used (on one machine only, with origin set exclusive on that machine). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719333 Title: CLVM not locking LV's properly even when set to exclusive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561390] Re: LVM - /var failed to mount during boot
On Thu, Oct 07, 2010 at 07:05:36AM -, Kelsey Thornton wrote: Some idiot thought it'd be a good idea if device mapper didn't respond to add events, like those during boot. Take their change out back and shoot it in the head. LP: #561390. Unless the kernel has been customised, udev add events issued by dm tell userspace nothing useful and must be ignored. Change events are the ones to act upon as they indicate that there is a device available for use. If you're having problems in this area, take a look at how the latest versions of other distros have packaged the upstream releases and made it all work together successfully e.g. Fedora/RHEL or SuSE (but not Debian). Alasdair -- LVM - /var failed to mount during boot https://bugs.launchpad.net/bugs/561390 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 593228] [NEW] Misleading error message with pvremove
On Sun, Jun 13, 2010 at 10:42:42AM -, Launchpad Bug Tracker wrote: Can't pvremove physical volume /dev/sdf1 of volume group vdr without -ff How did that get into the tree?! And messages are always supposed to use long forms of the options (--force) too. And a description is missing from the man page. This all needs improving... Alasdair -- Misleading error message with pvremove https://bugs.launchpad.net/bugs/593228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 460906] Re: disk/by-uuid/foo symlink points to snapshot rather than the origin
On Mon, Oct 26, 2009 at 01:44:51PM -, Scott James Remnant wrote: This is by design, the code in 65-dmsetup.rules is deliberately making the snapshot origin the *LOWEST* possible priority. Upstream I think we're going with giving the snapshot origin precedence. But none of these solutions is satisfactory - it is a multi-valued property. Either we find a way to recognise that, or we need to make it configurable within LVM so the end user can choose which behaviour they prefer. Alasdair -- disk/by-uuid/foo symlink points to snapshot rather than the origin https://bugs.launchpad.net/bugs/460906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 460906] Re: disk/by-uuid/foo symlink points to snapshot rather than the origin
On Mon, Oct 26, 2009 at 11:44:57PM +, Alasdair G Kergon wrote: But none of these solutions is satisfactory - it is a multi-valued property. Either we find a way to recognise that, or we need to make it configurable within LVM so the end user can choose which behaviour they prefer. We could eventually go further, and use the power of udev to have a trigger that automatically changes one of the UUIDs to make it unique. Alasdair -- disk/by-uuid/foo symlink points to snapshot rather than the origin https://bugs.launchpad.net/bugs/460906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 455441] [NEW] lvcreate -s hangs when creating a snapshot of a frozen xfs filesystem
On Mon, Oct 19, 2009 at 01:12:25PM -, Uwe Mesecke wrote: When trying to create a snapshot of a xfs filesystem, lvcreate hangs if the filesystem was previously frozen using xfs_freeze. Are you using a 2.6 kernel? Then the workaround is not to use xfs_freeze when creating snapshots! No device-mapper-based snapshots have ever needed it. Why do people persist in thinking incorrectly that XFS is the only filesystem that has to be told explicitly to do this? Device-mapper snapshots in *all* kernels provide this functionality automatically provided the filesystem supports it, which XFS does. Alasdair -- lvcreate -s hangs when creating a snapshot of a frozen xfs filesystem https://bugs.launchpad.net/bugs/455441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 363037] Re: dmsetup man page is obsolete
On Tue, Apr 21, 2009 at 07:45:52AM -, Sachin Garg wrote: The export option is also there in RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=438604 No it isn't. But there is a different related option missing from the upstream man page that we'll fix upstream. Alasdair -- a...@redhat.com -- dmsetup man page is obsolete https://bugs.launchpad.net/bugs/363037 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 363037] [NEW] dmsetup man page is obsolete
On Fri, Apr 17, 2009 at 06:05:50PM -, Sachin Garg wrote: This page does *not* document the export option added in August 2007. BTW The export option has not been accepted upstream: an alternative approach is being developed. Alasdair -- a...@redhat.com -- dmsetup man page is obsolete https://bugs.launchpad.net/bugs/363037 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332270] Re: udev repeatedly generates change events for the same block device(s)
On Mon, Feb 23, 2009 at 04:45:18PM -, Scott James Remnant wrote: There are two parts to this bug. The actual bug is being caused by lvm vgscan opening all block devices on the system writable and then closing them again, which triggers the inotify event. There seems to be no reason they cannot be opened readonly, since the only thing it does is call fstat() and read() on them. Good luck:-) Part #1 of the fix will be a patch to LVM to only open block devices with O_RDONLY I don't know which lines are the problem, but it's probably opening them for write in case it decides it needs to fix up the metadata. (It can't handle promotion from read-write so if any possible code path includes a write, it opens with write access.) Since the devices include any LVM PVs (which is what it's looking for), this gives you a recursive loop where LVM PVs appear to have been changed, so udev calls lvm vgscan again to update its tables. That's what needs fixing - vgscan is just the wrong approach here. Upstream (2.02.45) we made a start with a new class of 'pvs' output fields, Physical Volume Label Fields, e.g. pvs -o pv_name. If only these fields are specified, the code is meant not to scan and only access the devices specified on the command line. We need to sort out the right interface for adding one device at a time so you don't need vgscan at all. Alasdair -- a...@redhat.com -- udev repeatedly generates change events for the same block device(s) https://bugs.launchpad.net/bugs/332270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332270] Re: udev repeatedly generates change events for the same block device(s)
It's also worth trying it without any vgscans at all - it ought to cope without nowadays provided all commands access VGs by name i.e. 'vgchange -ay vg1' and never 'vgchange -ay'. It'll trigger a vgscan internally if it can't find a VG that was explicitly named. Alasdair -- a...@redhat.com -- udev repeatedly generates change events for the same block device(s) https://bugs.launchpad.net/bugs/332270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 282189] Re: dmsetup deps does not accurately report LVM dependencies, can cause boot failure
On Wed, Dec 17, 2008 at 03:27:39PM -, Tony Lewis wrote: Alasdair G. Kergon wrote: Surely that's it working as designed? dmsetup tells you about mapped devices available in the running kernel. I don't think so. dmsetup deps indicates the devices that your mapped device depends on. dmsetup has no access to the userspace LVM metadata where the information you appear to be seeking is stored. It is simply a convenient command-line interface to the libdevmapper library that is a wrapper around the device-mapper ioctls. Use a query tool like 'pvs' to find out what PVs belong to the VG containing a particular LV. Alasdair -- a...@redhat.com -- dmsetup deps does not accurately report LVM dependencies, can cause boot failure https://bugs.launchpad.net/bugs/282189 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 282189] Re: dmsetup deps does not accurately report LVM dependencies, can cause boot failure
On Tue, Dec 16, 2008 at 10:13:33PM -, Hugo Josefson wrote: I can confirm that this bug affects me too in Ubuntu 8.10. For me, the scenario is a little different (newly installed system where the VG has many PV:s, of which only one's extents are in use). dmsetup deps still only reports the PV whose extents are in use, and not all PV:s that are required for the VG to start. Surely that's it working as designed? dmsetup tells you about mapped devices available in the running kernel. Alasdair -- a...@redhat.com -- dmsetup deps does not accurately report LVM dependencies, can cause boot failure https://bugs.launchpad.net/bugs/282189 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 305940] [NEW] pvdisplay reporting wrong volume size
On Sun, Dec 07, 2008 at 10:29:50AM -, Christian Homagk wrote: Package: LVM2, 2.02.26.1ubuntu9 pvdisplay obviously reports the wrong size with TB untis: I would expect 6920 GB of free space. When I run sudo pvdisplay --units G: --- Physical volume --- PV Size 6919,74 GB / not usable 0,00 GB PE Size (KByte) 4096 Total PE 1649794 This is fine. But when I run sudo pvdisplay: --- Physical volume --- PV Size 6,29 TB / not usable 1,14 MB PE Size (KByte) 4096 Total PE 1649794 So, the digits after the decimal point (6,29 TB) are in the wrong order. This caused me some confusion... Looks OK to me - see references to --units on the man pages. The default is to use powers of 1024, but --units G asks for powers of 1000. Try '--units g' instead. Alasdair -- [EMAIL PROTECTED] -- pvdisplay reporting wrong volume size https://bugs.launchpad.net/bugs/305940 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239460] Re: Please update lvm2 to 2.02.39
Go for 2.02.42 which seems stable so far... -- Please update lvm2 to 2.02.39 https://bugs.launchpad.net/bugs/239460 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 274264] [NEW] lvcreate --type undocumented
On Thu, Sep 25, 2008 at 05:30:03AM -, Peter Cordes wrote: AFAICT, --type isn't documented in the man page or in /usr/share/doc/lvm2. And I didn't have any luck with google. It's an alternative way of specifying the type of segment to create e.g. mirror, snapshot, error, zero etc. E.g. lvcreate -s is treated internally as a shortcut for lvcreate --type snapshot. Maybe someone would submit a man page patch to the lvm-devel list... Alasdair -- [EMAIL PROTECTED] -- lvcreate --type undocumented https://bugs.launchpad.net/bugs/274264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [dm-crypt] Re: [Bug 267192] [NEW] Misleading cryptsetup error message
LVM2 tackles this by doing the library equivalent of 'dmsetup targets' and if the target is not listed it tries modprobe then checks again. Alasdair -- [EMAIL PROTECTED] -- Misleading cryptsetup error message https://bugs.launchpad.net/bugs/267192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 239460] [NEW] Please merge lvm2 2.02.35-1 (main) from Debian unstable (main)
Advise against that - none of the recent upstream releases has been stable. 2.02.38 (depends on a dm update too) might be OK. -- Please merge lvm2 2.02.35-1 (main) from Debian unstable (main) https://bugs.launchpad.net/bugs/239460 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 174032] lvresize fails attempting to call fsadm with --resizefs parameter
On Tue, Dec 04, 2007 at 10:46:22PM -, R. Denison wrote: lvresize --verbose --resizefs --size +1036 /dev/usb_vg/testvol1 It's a long story, but --resizefs is still not yet supported upstream. The good news is that someone sent me a reasonable-looking patch today and there's a good chance this will be available upstream in the next week or so. Alasdair -- [EMAIL PROTECTED] -- lvresize fails attempting to call fsadm with --resizefs parameter https://bugs.launchpad.net/bugs/174032 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 158106] pvmove cannot find physical volume
On Sun, Oct 28, 2007 at 06:04:18PM -, foolishchild wrote: I try 'sudo pvmove /dev/hda1' and get Physical Volume /dev/hda1 not found in Volume Group Big. PV Name /dev/mapper/hda1 Check major/minor numbers/symlinks to make sure they refer to the same device. And check it from the internal lvm shell too: sudo lvm vgscan pvmove /dev/mapper/hda1 Alasdair -- [EMAIL PROTECTED] -- pvmove cannot find physical volume https://bugs.launchpad.net/bugs/158106 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129285] dmraid says mirroring but isn't
On Mon, Jul 30, 2007 at 06:12:13PM -, justin wrote: [EMAIL PROTECTED]:~# lvdisplay I'm puzzled why there are no warning messages printed here. Please can you send the contents of /etc/lvm/lvm.conf and also the full output of 'vgscan -'? Alasdair -- [EMAIL PROTECTED] -- dmraid says mirroring but isn't https://bugs.launchpad.net/bugs/129285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129488] Re: insane default readahead settings on device and unused readahead setting in LVM
On Tue, Jul 31, 2007 at 09:06:14PM -, James Troup wrote: This is apparently a known issue upstream, but not considered a priority: Actually patches for better readahead support are being worked on by Zdenek Kabelac and are nearly ready. Alasdair -- [EMAIL PROTECTED] -- insane default readahead settings on device and unused readahead setting in LVM https://bugs.launchpad.net/bugs/129488 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 65813] Re: Edgy: pvmove (LVM) failes with device_mapper ioctl errors
On Tue, Mar 20, 2007 at 08:20:11PM -, tharkun wrote: My libdevmapper is pool/main/d/devmapper/libdevmapper1.02_1.02.07-1ubuntu2_i386.deb and I still get the same buggy behaviour. I repeat, libdevmapper 1.02_1.02.07 does NOT fix this bug. Is it this one upstream? Version 1.02.08 - 17 July 2006 == Fix corelog segment line. [In RHEL 4 the patch was added in 1.02.07-2 Tue May 16 2006]. Alasdair -- [EMAIL PROTECTED] -- Edgy: pvmove (LVM) failes with device_mapper ioctl errors https://launchpad.net/bugs/65813 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 84672] Re: [feisty] failures when creating snapshots in use: not deactivating
Common cause of that error is udev running stuff that opens and accesses the device while lvm2 is trying to remove it. Fix the udev rules so there's no attempt to open those devices. Long-term fix needs a new userspace notification mechanism: udev will notify lvm2 when it's finished whatever it's doing, and lvm2 will wait for that notification before proceeding. Also udev must totally ignore 'add' events from device-mapper devices and act instead on the 'change' events we added upstream recently. ['add' event is triggered in the kernel when the device number is reserved and the device is not yet usable - there are intrinsic races; 'change' is triggered when the device is ready for use incl. each time its constitution changes and udev ought to reprocess it.] Alasdair -- [EMAIL PROTECTED] -- [feisty] failures when creating snapshots in use: not deactivating https://launchpad.net/bugs/84672 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84821] Re: attempt to access beyond end of device when creating LVM snapshot
You need to improve your bug reporting skills:-) Exactly what userspace commands did you run with exactly what options? What is the architecture? (Arch chunksize interact.) You also need to say what userspace versions of lvm2 device-mapper you are using - it's not necessarily a kernel bug. There have been a lot of fixes to kernel device-mapper, including snapshots, since 2.6.15. So test against the latest upstream kernel and userspace packages if you can and see whether or not the problem has already been fixed there. -- attempt to access beyond end of device when creating LVM snapshot https://launchpad.net/bugs/84821 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84821] Re: attempt to access beyond end of device when creating LVM snapshot
Also give details if you have any layered devices - for example if you have md underneath dm. (There was a md+dm readahead bug fixed recently, for example.) -- attempt to access beyond end of device when creating LVM snapshot https://launchpad.net/bugs/84821 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 76421] Re: system crash when creating more than one snapshot of a lvm volume
On Fri, Jan 05, 2007 at 02:40:17PM -, Stephan Wienczny wrote: IMHO the kernel should check if the filesystem is already frozen and maybe increase a freeze counter to avoid the race. see the (not yet resolved) thread on linux-kernel: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex Alasdair -- [EMAIL PROTECTED] -- system crash when creating more than one snapshot of a lvm volume https://launchpad.net/bugs/76421 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 76421] Re: system crash when creating more than one snapshot of a lvm volume
On Fri, Jan 05, 2007 at 06:47:50AM -, acutler wrote: one seems to care). I can panic every 6.06 kernel if I remove the snapshot of a logical volume that has just been written to without kernel bugzilla 7040 ? (fixed upstream some time ago) Alasdair -- [EMAIL PROTECTED] -- system crash when creating more than one snapshot of a lvm volume https://launchpad.net/bugs/76421 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
