Re: VG backed storage pool start behavior.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It was a distro specific issue. Arch Linux has the lvm tools in /usr/sbin instead of /sbin. I made links for lvs, vgs, and vgchange and the issue cleared up. Reported a bug for the package.


On Wed, Feb 20, 2013 at 6:40 AM, Ján Tomko <jtomko@xxxxxxxxxx> wrote:
On 02/18/13 23:11, Luke Varnadore wrote:
> Libvirt 1.0.2-3
>
> I am unable to use vg storage pools that are shared with the host. I was
> able to do this without issue an update before this one. Wondering if
> anyone else is seeing this behavior.
>
> I am on an Arch Linux system but I can't see why that would matter yet.
>
> Here is the error I get when trying to start a pool defined from the
> shared VG that my host, and guests share:
>
> Error starting pool 'vg_nimbus': internal error Child process
> (/sbin/vgchange -aln vg_nimbus) unexpected exit status 5:   Can't
> deactivate volume group "vg_nimbus" with 7 open logical volume(s)

It looks like we're trying to deactivate the volumes when starting the
pool, which is what happens when we can't refresh the pool succesfully.

Deactivation fails, since some of the volumes are still open, and this
overwrites the previous error message.

Try looking in libvirtd.log if there is another error message before
this one.

Jan



--
Luke W Varnadore
727.697.7865
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]