linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: murali krishna <murali.marimekala@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, "Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: Clarification required about xfs_metadump and xfs_mdrestore
Date: Tue, 27 Sep 2016 21:29:33 -0400	[thread overview]
Message-ID: <CAOSFFygazt7umH314ZKXgbe0RrRCDL_0gvojHKnuGHxy_XZV+g@mail.gmail.com> (raw)
In-Reply-To: <20160927214129.GC27872@dastard>


[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]

Hi Dave,

Thanks for the clarification and inputs. Your support is much appreciated.

Murali

On Tue, Sep 27, 2016 at 5:41 PM, Dave Chinner <david@fromorbit.com> wrote:

> On Tue, Sep 27, 2016 at 01:27:12PM -0400, murali krishna wrote:
> > 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 ?
>
> The man page is simply stating the truth - metadump/restore are
> debugging tools used by XFS developers for obtaining information
> required for forensic analysis of filesystem failures.
>
> What you are wanting to do will not work, is not supported, and you
> get to keep all the broken bits to yourself if you try it.
> Every XFS developer you ask will say the same thing:
> xfsdump/encrypt/mkfs/xfs_restore is the only way to do what you want
> to do.
>
> -Dave.
> --
> Dave Chinner
> david@fromorbit.com
>

[-- Attachment #1.2: Type: text/html, Size: 1624 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2016-09-28  1:30 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
2016-09-27 21:41     ` Dave Chinner
2016-09-28  1:29       ` murali krishna [this message]

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=CAOSFFygazt7umH314ZKXgbe0RrRCDL_0gvojHKnuGHxy_XZV+g@mail.gmail.com \
    --to=murali.marimekala@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.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).