From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.com, gpiccoli@igalia.com
Subject: [PATCH 0/2 v2] btrfs-progs: mkfs: testing cloned-device
Date: Tue, 3 Oct 2023 11:46:12 +0800 [thread overview]
Message-ID: <cover.1696304038.git.anand.jain@oracle.com> (raw)
v2:
Worked on review comments from David.
--- v1 ---
This patchset adds support for testing cloned-device in mkfs.
So using mkfs.btrfs both option -U and -P a new device can be created
to match the FSID and UUID of an existing device. This is useful for
testing cloned-device.
Anand Jain (2):
btrfs-progs: document allowing duplicate fsid
btrfs-progs: add mkfs option for dev_uuid
Documentation/mkfs.btrfs.rst | 10 ++++++++--
mkfs/common.c | 8 +++++++-
mkfs/common.h | 5 +++++
mkfs/main.c | 16 +++++++++++++++-
4 files changed, 35 insertions(+), 4 deletions(-)
--
2.39.3
next reply other threads:[~2023-10-03 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 3:46 Anand Jain [this message]
2023-10-03 3:46 ` [PATCH 1/2] btrfs-progs: document allowing duplicate fsid Anand Jain
2023-10-03 3:46 ` [PATCH 2/2 v2] btrfs-progs: add mkfs option for dev_uuid Anand Jain
2023-10-17 23:49 ` [PATCH 0/2 v2] btrfs-progs: mkfs: testing cloned-device David Sterba
2023-10-19 1:32 ` Anand Jain
2023-10-19 11:59 ` David Sterba
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.1696304038.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=gpiccoli@igalia.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).