From: Christophe <c.baegert-listes@lixium.fr>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM crashed, no superblock on dozens of LVs even after vgcfgrestore
Date: Fri, 27 Mar 2015 12:00:55 +0100 [thread overview]
Message-ID: <55153867.80501@lixium.fr> (raw)
Hi,
I use LVM on Debian Wheezy, kernel 3.2.0-4-amd64, with several dozens of
LVs.
Every attempt of mounting any of these LVs says : can't read superblock
I can't imagine than each of all theses LVs were corrupted at the same time.
There should be a common problem for that. But which one ??? FYI I'm
using LVM -on-DRBD-on-LVM.
DBRD seems to be fine.
pvs
PV VG Fmt Attr PSize PFree
/dev/raidssd/drbd0 miroirtest lvm2 a-- 124,99g 9,99g
/dev/raidssd/drbd1 miroir1 lvm2 a-- 899,97g 0
/dev/raidssd/drbd2 miroir2 lvm2 a-- 899,97g 0
/dev/raidssd/drbd3 miroir1 lvm2 a-- 899,97g 0
/dev/raidssd/drbd4 miroir2 lvm2 a-- 899,97g 9,99g
/dev/raidssd/drbd5 miroir1 lvm2 a-- 929,97g 0
/dev/raidssd/drbd6 miroir2 lvm2 a-- 929,97g 1,70g
/dev/raidssd/drbd7 miroir1 lvm2 a-- 929,97g 17,88g
/dev/raidssd/drbd8 miroir2 lvm2 a-- 935,96g 157,64g
/dev/sda raidssd lvm2 a-- 3,64t 0
/dev/sdb raidssd lvm2 a-- 3,64t 0
cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
srcversion: 41C52C8CD882E47FB5AF767
0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate A r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
1: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate A r-----
ns:0 nr:10990235 dw:10990235 dr:0 al:0 bm:178 lo:0 pe:0 ua:0 ap:0
ep:1 wo:d oos:0
2: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate A r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
3: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate A r-----
ns:0 nr:21387 dw:21387 dr:0 al:0 bm:6 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d
oos:0
4: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate A r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
5: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate A r-----
ns:0 nr:2648 dw:2648 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
6: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate A r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
7: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate A r-----
ns:0 nr:59829829 dw:59829829 dr:0 al:0 bm:93 lo:0 pe:0 ua:0 ap:0
ep:1 wo:d oos:0
8: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate A r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
There was no error about that in the system logs.
Any idea about that ?
Regards,
--
Christophe
next reply other threads:[~2015-03-27 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 11:00 Christophe [this message]
2015-03-27 11:45 ` [linux-lvm] LVM crashed, no superblock on dozens of LVs even after vgcfgrestore Christian Schröder
2015-03-27 12:36 ` Christophe
2015-03-27 13:30 ` Christophe
2015-03-30 13:33 ` Jack Waterworth
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=55153867.80501@lixium.fr \
--to=c.baegert-listes@lixium.fr \
--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 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.