From: Mark Harmstone <mark@harmstone.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: btrfs-dump 20260330
Date: Mon, 30 Mar 2026 18:31:14 +0100 [thread overview]
Message-ID: <2f11087b-c1c8-499c-99ad-368dcead60c4@harmstone.com> (raw)
Hi all,
I have released version 20260330 of btrfs-dump, which given a btrfs
image produces a text-form representation of its metadata:
https://github.com/maharmstone/btrfs-dump
This version also includes btrfs-assemble, which does the reverse: given
a text file, it creates a corresponding btrfs image. This is useful for
creating deliberately invalid images for testing purposes - previously,
this was difficult to do without using a hex editor.
Changelog:
* Added remap_tree to incompat flags
* Fixed issue when dumping compressed inline extent
* Extra bytes on an item now get written out explicitly
* Spaces and special characters in file names now get escaped
* Added man page
* Added btrfs-assemble
Thanks
reply other threads:[~2026-03-30 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2f11087b-c1c8-499c-99ad-368dcead60c4@harmstone.com \
--to=mark@harmstone.com \
--cc=linux-btrfs@vger.kernel.org \
/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