linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Gang He <GHe@suse.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Do we have a way to clone the customer lvm2 environment?
Date: Thu, 12 Mar 2020 04:54:18 +0000	[thread overview]
Message-ID: <CH2PR18MB32064A3308D7D5BB3556EC47CFFD0@CH2PR18MB3206.namprd18.prod.outlook.com> (raw)

Hi Guys,

Sometimes we encountered some lvm2 meta-data damage (by lvm2 commands) problems.
Do we have a way to clone (or dump) the customer lvm2 environment? such like file system e2image tool.
for example, we can dump each pv(meta data + data(with file hole)) to a file, 
next we can rebuild the cloned lvm2 environment in local machine.
then, we can verify the fix in local machine with the tentative rpms before give them to the customers.  

Any suggestions for this kind of case?

Thanks
Gang

             reply	other threads:[~2020-03-12  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12  4:54 Gang He [this message]
2020-03-12  9:36 ` [linux-lvm] Do we have a way to clone the customer lvm2 environment? Zdenek Kabelac

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=CH2PR18MB32064A3308D7D5BB3556EC47CFFD0@CH2PR18MB3206.namprd18.prod.outlook.com \
    --to=ghe@suse.com \
    --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).