From: Bastian Blank <waldi@debian.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm2 2.01.12 fails to read lvm1 metadata
Date: Wed, 29 Jun 2005 14:58:31 +0200 [thread overview]
Message-ID: <20050629125831.GA23520@wavehammer.waldi.eu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]
Hi folks
I got another report, that snapshots with lvm1 metadata does not work.
Bastian
----- Forwarded message from Igor Belyi <belyi@users.sourceforge.net> -----
From: Igor Belyi <belyi@users.sourceforge.net>
To: Debian Bug Tracking System <315339@bugs.debian.org>
Subject: Bug#315339: installation of new lvm2 renders vg unusable
Date: Tue, 28 Jun 2005 19:11:49 -0400
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham
version=3.0.4
Package: lvm2
Version: 2.01.12-2
Followup-For: Bug #315339
Installing new lvm2 makes stripped VG unrecognizable.
Downgrading lvm2 back to 2.01.04-5 fixes the problem.
# vgdisplay lvmg
LV backup: inconsistent LE count 1832 != 3662
Internal error: LV segments corrupted in backup.
Volume group "lvmg" doesn't exist
Attached is the /etc/lvm/backup/lvmg config file for the group.
Igor
# Generated by LVM2: Tue Jun 28 16:41:34 2005
contents = "Text Format Volume Group"
version = 1
description = "Created *after* executing '/sbin/vgcfgbackup'"
creation_host = "leonid" # Linux leonid 2.6.11 #1 Wed Mar 2 09:29:56 EST 2005 i686
creation_time = 1119991294 # Tue Jun 28 16:41:34 2005
lvmg {
id = "BSy91n-ruZ9-cPDQ-aD8u-hNVI-NhxK-kzr4Rq"
seqno = 0
status = ["RESIZEABLE", "READ", "WRITE"]
system_id = "leonid1067528333"
extent_size = 65536 # 32 Megabytes
max_lv = 256
max_pv = 256
physical_volumes {
pv0 {
id = "yDDqdI-Zm8P-fcfz-veUd-3erD-lo7L-74LLT5"
device = "/dev/hda" # Hint only
status = ["ALLOCATABLE"]
pe_start = 65920
pe_count = 1831 # 57.2188 Gigabytes
}
pv1 {
id = "a2cuJy-QuIa-k4nx-eHdB-qTXB-4X0n-EoYa2L"
device = "/dev/hdc" # Hint only
status = ["ALLOCATABLE"]
pe_start = 65920
pe_count = 1831 # 57.2188 Gigabytes
}
}
logical_volumes {
backup {
id = "000000-0000-0000-0000-0000-0000-000000"
status = ["READ", "WRITE", "VISIBLE"]
allocation_policy = "normal"
read_ahead = 1024
segment_count = 1
segment1 {
start_extent = 0
extent_count = 3662 # 114.438 Gigabytes
type = "striped"
stripe_count = 2
stripe_size = 32 # 16 Kilobytes
stripes = [
"pv1", 0,
"pv0", 0
]
}
}
}
}
----- End forwarded message -----
--
Men of peace usually are [brave].
-- Spock, "The Savage Curtain", stardate 5906.5
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2005-06-29 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 12:58 Bastian Blank [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-22 7:46 [linux-lvm] lvm2 2.01.12 fails to read lvm1 metadata Bastian Blank
2005-06-22 14:58 ` AJ Lewis
2005-06-22 15:35 ` Alasdair G Kergon
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=20050629125831.GA23520@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--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).