From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs-progs: mkfs/rootdir: add hard link support
Date: Tue, 20 Aug 2024 13:15:41 +0930 [thread overview]
Message-ID: <cover.1724125282.git.wqu@suse.com> (raw)
[Changelog]
v2:
- Fix several grammar errors and change "can not" to more formal
"cannot"
- Initialize the temporary hardlink_entry structure as const
- Double quote the $nr_hardlink used in test case
With the recently reworked --rootdir support, although it solves several
hard link related problems, it splits the hard links into new inodes.
And on each split, it shows a warning on each file with hardlinks.
Although the split behavior doesn't cause any data corruption, it can
still be pretty noisy for rootfs creation, as there are a lot of distros
storing timezone files as hardlinks.
This patchset adds back the hard link detection and creation, with
enhanced handling to co-operate with --subvol option.
The details can be found in the first patch, with the new corner case
introduced by --subvol option.
The second patch enhances the existing --rootdir and --subvol test case
with extra corner cases like hard links, and hard links split by
subvolume boundary.
Qu Wenruo (2):
btrfs-progs: mkfs/rootdir: add hard link support
btrfs-progs: mkfs-tests: add hardlink related tests for --subvol
Documentation/mkfs.btrfs.rst | 13 ++
mkfs/rootdir.c | 199 +++++++++++++++++---
tests/mkfs-tests/036-rootdir-subvol/test.sh | 78 ++++++--
3 files changed, 247 insertions(+), 43 deletions(-)
--
2.46.0
next reply other threads:[~2024-08-20 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 3:45 Qu Wenruo [this message]
2024-08-20 3:45 ` [PATCH v2 1/2] btrfs-progs: mkfs/rootdir: add hard link support Qu Wenruo
2024-08-20 3:45 ` [PATCH v2 2/2] btrfs-progs: mkfs-tests: add hardlink related tests for --subvol Qu Wenruo
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=cover.1724125282.git.wqu@suse.com \
--to=wqu@suse.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;
as well as URLs for NNTP newsgroup(s).