From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: linux-xfs@vger.kernel.org, cem@kernel.org
Subject: Re: [PATCH V3 10/23] metadump: Define metadump v2 ondisk format structures and macros
Date: Tue, 1 Aug 2023 16:46:54 -0700 [thread overview]
Message-ID: <20230801234654.GQ11352@frogsfrogsfrogs> (raw)
In-Reply-To: <20230721094533.1351868-11-chandan.babu@oracle.com>
On Fri, Jul 21, 2023 at 03:15:20PM +0530, Chandan Babu R wrote:
> The corresponding metadump file's disk layout is as shown below,
>
> |------------------------------|
> | struct xfs_metadump_header |
> |------------------------------|
> | struct xfs_meta_extent 0 |
> | Extent 0's data |
> | struct xfs_meta_extent 1 |
> | Extent 1's data |
> | ... |
> | struct xfs_meta_extent (n-1) |
> | Extent (n-1)'s data |
> |------------------------------|
>
> The "struct xfs_metadump_header" is followed by alternating series of "struct
> xfs_meta_extent" and the extent itself.
>
> Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
For this patch,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
However: could you please post an update with the new metadump2 file
format for
https://git.kernel.org/pub/scm/fs/xfs/xfs-documentation.git/ ?
--D
> ---
> include/xfs_metadump.h | 68 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 68 insertions(+)
>
> diff --git a/include/xfs_metadump.h b/include/xfs_metadump.h
> index a4dca25c..50175ef0 100644
> --- a/include/xfs_metadump.h
> +++ b/include/xfs_metadump.h
> @@ -8,7 +8,9 @@
> #define _XFS_METADUMP_H_
>
> #define XFS_MD_MAGIC_V1 0x5846534d /* 'XFSM' */
> +#define XFS_MD_MAGIC_V2 0x584D4432 /* 'XMD2' */
>
> +/* Metadump v1 */
> typedef struct xfs_metablock {
> __be32 mb_magic;
> __be16 mb_count;
> @@ -23,4 +25,70 @@ typedef struct xfs_metablock {
> #define XFS_METADUMP_FULLBLOCKS (1 << 2)
> #define XFS_METADUMP_DIRTYLOG (1 << 3)
>
> +/*
> + * Metadump v2
> + *
> + * The following diagram depicts the ondisk layout of the metadump v2 format.
> + *
> + * |------------------------------|
> + * | struct xfs_metadump_header |
> + * |------------------------------|
> + * | struct xfs_meta_extent 0 |
> + * | Extent 0's data |
> + * | struct xfs_meta_extent 1 |
> + * | Extent 1's data |
> + * | ... |
> + * | struct xfs_meta_extent (n-1) |
> + * | Extent (n-1)'s data |
> + * |------------------------------|
> + *
> + * The "struct xfs_metadump_header" is followed by alternating series of "struct
> + * xfs_meta_extent" and the extent itself.
> + */
> +struct xfs_metadump_header {
> + __be32 xmh_magic;
> + __be32 xmh_version;
> + __be32 xmh_compat_flags;
> + __be32 xmh_incompat_flags;
> + __be64 xmh_reserved;
> +} __packed;
> +
> +/*
> + * User-supplied directory entry and extended attribute names have been
> + * obscured, and extended attribute values are zeroed to protect privacy.
> + */
> +#define XFS_MD2_INCOMPAT_OBFUSCATED (1 << 0)
> +
> +/* Full blocks have been dumped. */
> +#define XFS_MD2_INCOMPAT_FULLBLOCKS (1 << 1)
> +
> +/* Log was dirty. */
> +#define XFS_MD2_INCOMPAT_DIRTYLOG (1 << 2)
> +
> +/* Dump contains external log contents. */
> +#define XFS_MD2_INCOMPAT_EXTERNALLOG (1 << 3)
> +
> +struct xfs_meta_extent {
> + /*
> + * Lowest 54 bits are used to store 512 byte addresses.
> + * Next 2 bits is used for indicating the device.
> + * 00 - Data device
> + * 01 - External log
> + */
> + __be64 xme_addr;
> + /* In units of 512 byte blocks */
> + __be32 xme_len;
> +} __packed;
> +
> +#define XME_ADDR_DEVICE_SHIFT 54
> +
> +#define XME_ADDR_DADDR_MASK ((1ULL << XME_ADDR_DEVICE_SHIFT) - 1)
> +
> +/* Extent was copied from the data device */
> +#define XME_ADDR_DATA_DEVICE (0ULL << XME_ADDR_DEVICE_SHIFT)
> +/* Extent was copied from the log device */
> +#define XME_ADDR_LOG_DEVICE (1ULL << XME_ADDR_DEVICE_SHIFT)
> +
> +#define XME_ADDR_DEVICE_MASK (3ULL << XME_ADDR_DEVICE_SHIFT)
> +
> #endif /* _XFS_METADUMP_H_ */
> --
> 2.39.1
>
next prev parent reply other threads:[~2023-08-01 23:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 9:45 [PATCH V3 00/23] Metadump v2 Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 01/23] metadump: Use boolean values true/false instead of 1/0 Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 02/23] mdrestore: Fix logic used to check if target device is large enough Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 03/23] metadump: Declare boolean variables with bool type Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 04/23] metadump: Define and use struct metadump Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 05/23] metadump: Add initialization and release functions Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 06/23] metadump: Postpone invocation of init_metadump() Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 07/23] metadump: Introduce struct metadump_ops Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 08/23] metadump: Introduce metadump v1 operations Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 09/23] metadump: Rename XFS_MD_MAGIC to XFS_MD_MAGIC_V1 Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 10/23] metadump: Define metadump v2 ondisk format structures and macros Chandan Babu R
2023-08-01 23:46 ` Darrick J. Wong [this message]
2023-07-21 9:45 ` [PATCH V3 11/23] metadump: Define metadump ops for v2 format Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 12/23] xfs_db: Add support to read from external log device Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 13/23] metadump: Add support for passing version option Chandan Babu R
2023-07-21 9:45 ` [PATCH V3 14/23] mdrestore: Declare boolean variables with bool type Chandan Babu R
2023-07-21 9:57 ` [PATCH V3 00/23] Metadump v2 Chandan Babu R
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 4:35 Chandan Babu R
2023-07-24 4:35 ` [PATCH V3 10/23] metadump: Define metadump v2 ondisk format structures and macros Chandan Babu R
2023-08-01 23:47 ` Darrick J. Wong
2023-08-02 13:08 ` Chandan Babu R
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=20230801234654.GQ11352@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=linux-xfs@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