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 becau
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 '
*** 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
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
--
Yo
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 Wed, 02 Jan 2013 11:11:41 +0100
> Do we still want it in Ubuntu?
It it
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 Wed, 02 Jan 2013 11:11:41 +0100
It it certainly not dead upstream and d
*** 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
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
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
T
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
positiv
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
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 paral
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 sub
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
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 (la
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 fiel
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 op
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/+sour
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 loc
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/612
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 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, wh
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.ubun
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 para
--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
h
Change message upstream:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/tools/pvremove.c.diff?r1=1.32&r2=1.33&cvsroot=lvm2&f=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:
Misleadi
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
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
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
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 pre
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
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 dev
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...@redh
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
h
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
--
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 t
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
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 t
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
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.u
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. l
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
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 Ubu
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 thi
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 che
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
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 defau
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 - 1
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'
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
ubunt
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.
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
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
53 matches
Mail list logo
