linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
* [linux-lvm] How to repair superblock is corrupt
@ 2020-05-28  7:35 lampahome
  2020-05-28  8:14 ` Gionatan Danti
  0 siblings, 1 reply; 2+ messages in thread
From: lampahome @ 2020-05-28  7:35 UTC (permalink / raw)
  To: linux-lvm

I create a vg1 on one SSD and create a lv1 in vg1.
Then I run:
sudo thin_check /dev/mapper/vg1-lv1

It shows:
examining superblock
  superblock is corrupt
    bad checksum in superblock

Can someone teach me how to fix corrupted superblock?

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [linux-lvm] How to repair superblock is corrupt
  2020-05-28  7:35 [linux-lvm] How to repair superblock is corrupt lampahome
@ 2020-05-28  8:14 ` Gionatan Danti
  0 siblings, 0 replies; 2+ messages in thread
From: Gionatan Danti @ 2020-05-28  8:14 UTC (permalink / raw)
  To: LVM general discussion and development; +Cc: lampahome

Il 2020-05-28 09:35 lampahome ha scritto:
> I create a vg1 on one SSD and create a lv1 in vg1.
> Then I run:
> sudo thin_check /dev/mapper/vg1-lv1
> 
> It shows:
> examining superblock
>   superblock is corrupt
>     bad checksum in superblock
> 
> Can someone teach me how to fix corrupted superblock?

Hi, thin_check should be run against the metadata device (more 
precisely, against a snapshot of the metadata device).

I suggest you reading thin_check/thin_dump man pages: 
https://www.systutorials.com/docs/linux/man/8-thin_check/

Regards.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it [1]
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-05-28  8:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-28  7:35 [linux-lvm] How to repair superblock is corrupt lampahome
2020-05-28  8:14 ` Gionatan Danti

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).