From: Mike Snitzer <snitzer@redhat.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Backup superblock for thin provision?
Date: Mon, 16 May 2016 14:55:19 -0400 [thread overview]
Message-ID: <20160516185518.GA3320@redhat.com> (raw)
In-Reply-To: <5735AEE4.4080402@assyoma.it>
On Fri, May 13 2016 at 6:39am -0400,
Gionatan Danti <g.danti@assyoma.it> wrote:
> Hi all,
> using thin provisioning in production machines (using it mostly for
> its fast snapshot support, rather than for thin provision / storage
> overcommit by itself), I wonder what to do if a critical metadata
> corruption, as the loss of the superblock, should happen.
>
> Filesystems generally have some backup copy of the superblock;
> should the primary one fail, another copy can be used.
>
> So I have the following questions:
> - how about thin LVM? Has it a backup superblock somewhere?
> - how can the metadata be reliable backupped without shutting down
> the volume?
> - more generally, how to deal with metadata backup? Does
> vgcfgrestore works for thin volumes?
>
> Thank you all.
There is more to the thinp metadata than just the metadata superblock.
The DM thin-pool's metadata device was purposely split out from the data
device to allow for additional metadata fault protection using RAID.
I'll defer to the LVM developers for if/how LVM can be used to have
thinp metadata redundancy even if you don't have multiple devices to be
able to use a conventional RAID device.
next prev parent reply other threads:[~2016-05-16 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 10:39 [linux-lvm] Backup superblock for thin provision? Gionatan Danti
2016-05-16 18:55 ` Mike Snitzer [this message]
2016-05-17 9:10 ` Zdenek Kabelac
2016-05-17 13:22 ` Gionatan Danti
2016-05-17 13:18 ` Gionatan Danti
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=20160516185518.GA3320@redhat.com \
--to=snitzer@redhat.com \
--cc=g.danti@assyoma.it \
--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.