From: murali krishna <murali.marimekala@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs@oss.sgi.com
Subject: Re: Clarification required about xfs_metadump and xfs_mdrestore
Date: Tue, 27 Sep 2016 13:27:12 -0400 [thread overview]
Message-ID: <CAOSFFyhP251ifYzWtRfcStxX7oy78EDvqWfi0=2h4GhTv4=pJw@mail.gmail.com> (raw)
In-Reply-To: <20160927170443.GR9314@birch.djwong.org>
[-- Attachment #1.1: Type: text/plain, Size: 2174 bytes --]
Hi Darrick,
Thanks for the response.
Could you please clarify if there is any strong reason behind in stating to
use xfs_metadump and xfs_mdrestore as just debugging tools in their
respective man pages ?
We tried xfsdump, its backing up the rtdev partition (/dev/sda1) as well. I
have around 450GB worth of recordings in my /dev/sda1 (rtdev).
I don't want to use any intermediate storage to backup all these data.
Yes, my aim is to backup the metadata (dont want to touch my rtdev) on
/dev/sda2, reformat "/dev/sda2" with crypt layer, restore metadata back on
/dev/sda2.
At the end, I am expecting my rtdev untouched and should automatically
appear after encrypting my /dev/sda2.
Note:
/dev/sda2- xfs partition
/dev/sda1 - xfs realtime partition
Thank you,
Murali
On Tue, Sep 27, 2016 at 1:04 PM, Darrick J. Wong <darrick.wong@oracle.com>
wrote:
> On Tue, Sep 27, 2016 at 09:49:11AM -0400, murali krishna wrote:
> > Hi All,
> >
> > Got your email id from Nathan Scott.
> >
> > Could you please clarify the reasons behind stating below statement in
> > xfs_metadump man page.
> >
> >
> >
> > *xfs_metadump should not be used for any purposes other than for
> > debugging and reporting filesystem problems*
> > Man page: http://man7.org/linux/man-pages/man8/xfs_metadump.8.html
> >
> > I am trying to encrypt my existing xfs drive (/dev/sda2) and would like
> to
> > backup metadata using xfs_metadump and restore it back using
> xfs_mdrestore
> > after encrypting my drive. In order to retain entire contents of my
> > realtime partition (/dev/sda1), I need to perform this step.
> >
> > Can I use xfs_metadump to backup meta-data of xfs and restore it back
> > successfully ?
> > Why xfs_metadump should be specifically used as debugging tool ? Please
> > clarify ?
>
> Uh.... if your goal is to back up data, reformat the storage with a crypto
> layer, and then restore the data, why not just use xfsdump/xfsrestore?
> Your data will end up all nicely defragmented, too.
>
> --D
>
> >
> > Thanks in Advance,
> > Murali
>
> > _______________________________________________
> > xfs mailing list
> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
>
>
[-- Attachment #1.2: Type: text/html, Size: 3258 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-09-27 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 13:49 Clarification required about xfs_metadump and xfs_mdrestore murali krishna
2016-09-27 16:35 ` Eric Sandeen
2016-09-27 17:04 ` Darrick J. Wong
2016-09-27 17:14 ` Eric Sandeen
2016-09-27 17:27 ` murali krishna [this message]
2016-09-27 21:41 ` Dave Chinner
2016-09-28 1:29 ` murali krishna
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='CAOSFFyhP251ifYzWtRfcStxX7oy78EDvqWfi0=2h4GhTv4=pJw@mail.gmail.com' \
--to=murali.marimekala@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=xfs@oss.sgi.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).