From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org, zlang@redhat.com
Subject: Re: [PATCH V3 2/5] common/xfs: Add function to detect support for metadump v2
Date: Thu, 11 Jan 2024 09:21:19 -0800 [thread overview]
Message-ID: <20240111172119.GC722968@frogsfrogsfrogs> (raw)
In-Reply-To: <20240111115913.1638668-3-chandanbabu@kernel.org>
On Thu, Jan 11, 2024 at 05:28:26PM +0530, Chandan Babu R wrote:
> This commit defines a new function to help detect support for metadump v2.
>
> Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
Looks good,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> common/xfs | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/common/xfs b/common/xfs
> index 38094828..fc744489 100644
> --- a/common/xfs
> +++ b/common/xfs
> @@ -698,6 +698,12 @@ _xfs_mdrestore() {
> $XFS_MDRESTORE_PROG $options "${metadump}" "${device}"
> }
>
> +_scratch_metadump_v2_supported()
> +{
> + $XFS_DB_PROG -c "help metadump" $SCRATCH_DEV | \
> + grep -q "Metadump version to be used"
> +}
> +
> # Snapshot the metadata on the scratch device
> _scratch_xfs_metadump()
> {
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-01-11 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 11:58 [PATCH V3 0/5] Add support for testing XFS metadump v2 Chandan Babu R
2024-01-11 11:58 ` [PATCH V3 1/5] common/xfs: Do not append -a and -o options to metadump Chandan Babu R
2024-01-11 11:58 ` [PATCH V3 2/5] common/xfs: Add function to detect support for metadump v2 Chandan Babu R
2024-01-11 17:21 ` Darrick J. Wong [this message]
2024-01-11 11:58 ` [PATCH V3 3/5] _scratch_xfs_mdrestore: Pass scratch log device when applicable Chandan Babu R
2024-01-11 11:58 ` [PATCH V3 4/5] xfs: Add support for testing metadump v2 Chandan Babu R
2024-01-12 2:18 ` Darrick J. Wong
2024-01-11 11:58 ` [PATCH V3 5/5] xfs: Check correctness of metadump/mdrestore's ability to work with dirty log Chandan Babu R
2024-01-12 2:20 ` Darrick J. Wong
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=20240111172119.GC722968@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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