linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christophe <c.baegert-listes@lixium.fr>
To: linux-lvm@redhat.com, cs@deriva.de
Subject: Re: [linux-lvm] LVM crashed, no superblock on dozens of LVs even after vgcfgrestore
Date: Fri, 27 Mar 2015 14:30:02 +0100	[thread overview]
Message-ID: <55155B5A.8060003@lixium.fr> (raw)
In-Reply-To: <55154ECD.1070707@lixium.fr>

Hi again,

i still now have a last LV saying "can't read superblock"
lvs says :
  "nfspostgres     miroir2    -wi-d--- 500,00g"

which means 'device present without tables'

and lvdisplay :
   --- Logical volume ---
   LV Path                /dev/miroir2/nfspostgres
   LV Name                nfspostgres
   VG Name                miroir2
   LV UUID                wPB72R-ZGLS-x1ww-0lgT-D6bz-ZA6S-h6PrOe
   LV Write Access        read/write
   LV Creation host, time host6filer2, 2014-06-02 00:40:01 +0200
   LV Status              available
   # open                 0
   LV Size                500,00 GiB
   Current LE             128000
   Segments               1
   Allocation             inherit
   Read ahead sectors     auto
   - currently set to     256
   Block device           253:35


I restored the LVM table of yesterday which included already this LV, 
and all the other LVs came back without problem.

With ext4, I could search for another superblock, I didn't find the 
command for xfs, maybe it exists ?

Any idea ?

Regards,

-- 
Christophe

  reply	other threads:[~2015-03-27 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 11:00 [linux-lvm] LVM crashed, no superblock on dozens of LVs even after vgcfgrestore Christophe
2015-03-27 11:45 ` Christian Schröder
2015-03-27 12:36   ` Christophe
2015-03-27 13:30     ` Christophe [this message]
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=55155B5A.8060003@lixium.fr \
    --to=c.baegert-listes@lixium.fr \
    --cc=cs@deriva.de \
    --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).