All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joschi Brauchle <joschi.brauchle@tum.de>
To: Marian Csontos <mcsontos@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgremove fails to remove empty VG (v2.02.98)
Date: Thu, 24 Jan 2013 09:09:47 +0100	[thread overview]
Message-ID: <5100EC4B.50306@tum.de> (raw)
In-Reply-To: <5100C5E5.8040603@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1744 bytes --]

Thanks for the detailed instructions, here are (some of) the missing 
gaps :-)

>> I get the following error with lvm2.02.98:
>> -----------
>> #/sbin/vgdisplay --units k -v 'system'
>>
>> --- Volume group ---
>> VG Name system
>> System ID
>> Format lvm2
>> Metadata Areas 1
>> Metadata Sequence No 13
>> VG Access read/write
>> VG Status resizable
>> MAX LV 0
>> Cur LV 0
>> Open LV 0
>> Max PV 0
>> Cur PV 1
>> Act PV 1
>> VG Size 104669184.00 KiB
>> PE Size 4096.00 KiB
>> Total PE 25554
>> Alloc PE / Size 0 / 0 KiB
>> Free PE / Size 25554 / 104669184.00 KiB
>> VG UUID Qs0uaZ-L88n-tC7T-fZQj-sgJY-2yRX-Dlt2Cr
>>
>> --- Physical volumes ---
>> PV Name /dev/sda3
>> PV UUID wzGjXi-F2lT-d2d4-l5a6-EmfM-W838-YxaFIh
>> PV Status allocatable
>> Total PE / Free PE 25554 / 25554
>> -----------
>>
>> VG system is empty, but still:
>> -----------
>> # /sbin/vgremove 'system'
>> -----------
>> failes with status code 5, which means 'can't remove volume group
>> containing logical volumes' (from man page).
>>
> 0. Which distro?
openSUSE 12.3 Beta 1 - Problem happens during installation, where an 
existing VGroup shall be removed.
>
> 1. lvmdump -ma
attached (hope that's ok)

> 2. vgremove -vvvv &> vgremove-dirty.out
http://pastebin.com/cmek1bYi

> 3. ps aux | grep lvmetad
Not running, no processes found. Skipping the remaining steps...
>
> 3.1 if so, the issue is likely to go away after restarting it. If you
> `gcore` or `kill -SEGV` it to get a core dump it may help us.
> 3.2 do another lvmdump here, to get "updated" data after lvmdump restart
> 3.3 retry 'vgremove -vvvv &> vgremove-reloaded.out'
> 4. pastebin the vgremove-dirty.out and we will be able to tell more then.

[-- Attachment #1.2: lvmdump-st-test-pxeinstall-2013012475030.tgz --]
[-- Type: application/x-compressed-tar, Size: 21316 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4607 bytes --]

  reply	other threads:[~2013-01-24  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 20:56 [linux-lvm] vgremove fails to remove empty VG (v2.02.98) Joschi Brauchle
2013-01-24  5:25 ` Marian Csontos
2013-01-24  8:09   ` Joschi Brauchle [this message]
2013-01-24 10:44     ` Marian Csontos
2013-01-24  5:50 ` mohammad azimi
2013-01-24 10:28   ` Joschi Brauchle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5100EC4B.50306@tum.de \
    --to=joschi.brauchle@tum.de \
    --cc=linux-lvm@redhat.com \
    --cc=mcsontos@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.