| To: | murali krishna <murali.marimekala@xxxxxxxxx> |
|---|---|
| Subject: | Re: Clarification required about xfs_metadump and xfs_mdrestore |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 28 Sep 2016 07:41:29 +1000 |
| Cc: | "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAOSFFyhP251ifYzWtRfcStxX7oy78EDvqWfi0=2h4GhTv4=pJw@xxxxxxxxxxxxxx> |
| References: | <CAOSFFyjWR4ASud5aSoYTJKweWA244oMwT9_LRSzwnr0Qftg7Eg@xxxxxxxxxxxxxx> <20160927170443.GR9314@xxxxxxxxxxxxxxxx> <CAOSFFyhP251ifYzWtRfcStxX7oy78EDvqWfi0=2h4GhTv4=pJw@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Right Contacts, Amy Walsh |
|---|---|
| Next by Date: | Re: [PATCH v3] tests/generic: test xfs log recovery metadata LSN ordering, Dave Chinner |
| Previous by Thread: | Re: Clarification required about xfs_metadump and xfs_mdrestore, murali krishna |
| Next by Thread: | Re: Clarification required about xfs_metadump and xfs_mdrestore, murali krishna |
| Indexes: | [Date] [Thread] [Top] [All Lists] |