From: Lukas Czerner <lczerner@redhat.com>
To: "Filip Štědronský" <r.lkml@regnarg.cz>
Cc: linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: Re: Any way to dump ext4 filesystem without file data blocks? (for later analysis)
Date: Thu, 30 Apr 2020 16:03:09 +0200 [thread overview]
Message-ID: <20200430140309.ndt5ao72evhhppeh@work> (raw)
In-Reply-To: <20200430134409.i5cxmmnbryx5hbui@baerbar.localdomain>
On Thu, Apr 30, 2020 at 03:44:09PM +0200, Filip Štědronský wrote:
> Hello,
>
> I have experienced several mysterious ext4 issues on remote machines
> with poor internet connection (mobile broadband) that are not easily
> physically accessible.
>
> I would like to download the filesystem image from the remote machine
> for local investigation but the partition is rather large (500GB in
> one instance) and I cannot easily upload that much data over the
> mobile connection.
>
> Is there any way to extract only filesystem metadata (superblock,
> inodes, directory data blocks, etc.) from the partition but not
> file data blocks? Ideally so that I could then reconstruct an
> identical filesystem image, only with file data blocks zeroed out.
>
> It seems it should be straightforwad to write such a tool but before
> I start doing so, I wanted to check whether somebody hasn't already
> written one. (It seems this might be a common enough need when
> debugging and developing filesystems.) Short googling around and
> searching list archive did not reveal anything.
>
> Thanks for any pointers.
>
> Filip Stedronsky
Hello Filip,
indeed there is a tool exactly for this purpose. It is called e2image
and it's part of the e2fsprogs. The manual page also have some useful
examples of how to use it.
Good luck.
-Lukas
prev parent reply other threads:[~2020-04-30 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 13:44 Any way to dump ext4 filesystem without file data blocks? (for later analysis) Filip Štědronský
2020-04-30 14:03 ` Lukas Czerner [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=20200430140309.ndt5ao72evhhppeh@work \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=r.lkml@regnarg.cz \
--cc=tytso@mit.edu \
/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