From: Dave Chinner <david@fromorbit.com>
To: Stefan Ring <stefanrin@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Collecting aged XFS profiles
Date: Thu, 20 Jul 2017 13:02:52 +1000 [thread overview]
Message-ID: <20170720030252.GT17762@dastard> (raw)
In-Reply-To: <CAAxjCEzZ2Q0wL=nhGVHVtK3M5Ws3MQdrUNKm3jJKO+1y-wxTkw@mail.gmail.com>
On Wed, Jul 19, 2017 at 11:08:41PM +0200, Stefan Ring wrote:
> On Wed, Jul 19, 2017 at 5:20 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
> > On 07/19/2017 02:59 AM, Stefan Ring wrote:
> >> I have created a metadump that is 1GB in size, xz-compressed. However,
> >> by running strings on it I find that there are many identifiable
> >> remains inside, and I cannot legally pass this on.
> >
> > newer metadump should correct that problem, and is a read-only tool,
> > so should be (tm) perfectly safe (tm). You could run it out of a built
> > git repo, via the xfs_db commands.
> >
> >> The question is: can I import this metadata image in a VM and recreate
> >> the metadata image from there, using modern xfsprogs? Will this
> >> preserve most of the relevant information?
> >
> > yes, that would work too. (mdrestore followed by or piped through metadump)
> > If you find significant strings in that result please let me know :)
>
> There is still quite a lot of stuff that should not be there (pasted
> selectively while scrolling over it via less):
[snip]
This stuff could all be in the journal. This is why I said "metadump
will first need to be modified to avoid dumping the journal".
Shouldn't be too hard - we already avoid dumping the journal when it
is external....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-07-20 3:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 0:11 Collecting aged XFS profiles Saurabh Kadekodi
2017-07-16 2:57 ` Eric Sandeen
2017-07-17 19:00 ` Stefan Ring
2017-07-17 23:48 ` Dave Chinner
2017-07-18 5:45 ` Saurabh Kadekodi
2017-07-19 7:59 ` Stefan Ring
2017-07-19 15:20 ` Eric Sandeen
2017-07-19 21:08 ` Stefan Ring
2017-07-19 22:00 ` Eric Sandeen
2017-07-20 7:52 ` Stefan Ring
2017-07-20 14:27 ` Eric Sandeen
2017-07-20 20:15 ` Stefan Ring
2017-07-20 20:21 ` Eric Sandeen
2017-07-20 3:02 ` Dave Chinner [this message]
2017-07-20 3:55 ` Eric Sandeen
2017-07-20 4:38 ` Dave Chinner
2017-07-20 14:24 ` Eric Sandeen
2017-07-20 22:27 ` Dave Chinner
2017-07-20 22:48 ` Eric Sandeen
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=20170720030252.GT17762@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=stefanrin@gmail.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