[linux-lvm] LVM crashed, no superblock on dozens of LVs even after vgcfgrestore
jack at redhat.com
Mon Mar 30 13:33:39 UTC 2015
Does the device actually exist here? I usually see these types of errors
when there is something wrong with the PV. More information should be
available via dmesg during activation.
# lvchange -ay vgname/lvname
As for the xfs file-system, i'd recommend reaching out to the xfs
community if you believe your lvm stack is intact. Even if it's not,
they may be able to provide some insight.
Jack Waterworth, Red Hat Certified Architect
OpenStack Technical Support North America
Red Hat Global Support Services ( 1.888.467.3342 )
On 03/27/2015 09:30 AM, Christophe wrote:
> 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 ?
More information about the linux-lvm