From: lejeczek <peljasz@yahoo.co.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>,
David Teigland <teigland@redhat.com>
Subject: Re: [linux-lvm] recovery of a VG - how?
Date: Tue, 15 Oct 2019 16:30:14 +0100 [thread overview]
Message-ID: <9ce34b5b-0c44-429b-c74d-a20ba565c397@yahoo.co.uk> (raw)
In-Reply-To: <20191007164218.GA4398@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
On 07/10/2019 17:42, David Teigland wrote:
> On Mon, Oct 07, 2019 at 05:25:15PM +0100, lejeczek wrote:
>> hi guys
>>
>> I have a VG which I try to restore:
>>
>> $ vgcfgrestore --file /etc/lvm/archive/chenbro0.0_00308-2121179640.vg chenbro0.0
>> /dev/mapper/chenbro_a: Checksum error at offset 428544
>> Couldn't read volume group metadata from /dev/mapper/chenbro_a.
>> Metadata location on /dev/mapper/chenbro_a at 428544 has invalid summary for VG.
> The latest upstream version of lvm has some improvements to help recover
> from problems like this. So, you could try building lvm 2.03.05, and
> running 'vgck --updatemetadata'. Otherwise, the old approach has been to
> use pvcreate with --restorefile and --uuid, followed by vgcfgrestore.
> (I'd experiment with that using some test devices if possible.)
> Dave
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
also, is it possible to stop monitoring, or stop whatever is responsible
for flooding the logs with:
...
lrmd[14636]: notice: chenbro0.1-raid5_monitor_20000:419255:stderr [
Couldn't read volume group metadata from /dev/mapper/chenbro_m. ]
...
for a time being?
many thanks, L.
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1787 bytes --]
prev parent reply other threads:[~2019-10-15 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 16:25 [linux-lvm] recovery of a VG - how? lejeczek
2019-10-07 16:42 ` David Teigland
2019-10-15 15:20 ` lejeczek
2019-10-15 15:30 ` lejeczek [this message]
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=9ce34b5b-0c44-429b-c74d-a20ba565c397@yahoo.co.uk \
--to=peljasz@yahoo.co.uk \
--cc=linux-lvm@redhat.com \
--cc=teigland@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).