linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Volume group inconsistent
Date: Mon, 09 Feb 2015 10:34:48 +0100	[thread overview]
Message-ID: <54D87F38.4010303@redhat.com> (raw)
In-Reply-To: <CAPcfVV_VVvYDf0oa7pZZ1iFkK6XJDBM4wYU9=EnYpCo4ogrbjQ@mail.gmail.com>

Dne 7.2.2015 v 16:47 Marcos Dutra napsal(a):
> Hi everybody,
>
> Yesterday some storage discs of my VG was with missing status
> /dev/mapper/plt-01                                        platinum       lvm2
> a-m  500.00g   24.95g
>    /dev/mapper/plt-02                                        platinum
> lvm2 a-m  500.00g   12.93g
>
> I tried recover the discs and I used the command:
> # vgextend --restoremissing platinum /dev/mapper/plt-01
>
> It worked, removing missing status, but I did a big mistake, i tried to run
> this command with multiple discs:
> # vgextend --restoremissing platinum /dev/mapper/plt-0[2-9]
>
> After that when I ran pvs command the output shows me checksum error:
>    /dev/mapper/plt-04: Checksum error
>    /dev/mapper/plt-06: Checksum error
>    /dev/mapper/plt-01: Checksum error
>    Couldn't read volume group metadata.
>    /dev/mapper/plt-02: Checksum error
>    Couldn't read volume group metadata.
>    /dev/mapper/plt-03: Checksum error
>
> I tried restore metadata without success:
> # vgcfgrestore -f platinum_02336-1600706364.vg
> <http://platinum_02336-1600706364.vg> platinum


Without having access to your current metadata - it's hard to give
proper advice.


So please attach  'vgcfgbackup' of your current setup.

Have you tried to 'extend' your existing vg   'plt' with referencing LVs from 
itself???
Is 'plt' VG ?

Zdenek

  reply	other threads:[~2015-02-09  9:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 15:47 [linux-lvm] Volume group inconsistent Marcos Dutra
2015-02-09  9:34 ` Zdenek Kabelac [this message]
2015-02-09 16:37   ` Marcos Dutra
2015-02-11 11:17     ` service hofman
2015-02-11 11:19       ` service hofman
2015-02-11 21:45         ` Marcos Dutra
2015-02-11 14:27     ` Zdenek Kabelac
2015-02-11 18:35       ` Marcos Dutra
2015-02-11 23:49       ` service hofman
2015-02-12 13:57         ` Marcos Dutra
2015-02-13 20:37           ` service hofman
2015-02-23 18:00             ` Marcos Dutra

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=54D87F38.4010303@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).