From: Chandan Babu R <chandanrlinux@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/5] xfs: dump log intent items that cannot be recovered due to corruption
Date: Fri, 06 Aug 2021 17:11:46 +0530 [thread overview]
Message-ID: <87v94iiyuw.fsf@garuda> (raw)
In-Reply-To: <162814687097.2777088.3937845877884086271.stgit@magnolia>
On 05 Aug 2021 at 00:01, "Darrick J. Wong" <djwong@kernel.org> wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> If we try to recover a log intent item and the operation fails due to
> filesystem corruption, dump the contents of the item to the log for
> further analysis.
>
Looks good to me.
Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> fs/xfs/xfs_bmap_item.c | 3 +++
> fs/xfs/xfs_extfree_item.c | 3 +++
> fs/xfs/xfs_refcount_item.c | 3 +++
> fs/xfs/xfs_rmap_item.c | 3 +++
> 4 files changed, 12 insertions(+)
>
>
> diff --git a/fs/xfs/xfs_bmap_item.c b/fs/xfs/xfs_bmap_item.c
> index e3a691937e92..3d6f70da8820 100644
> --- a/fs/xfs/xfs_bmap_item.c
> +++ b/fs/xfs/xfs_bmap_item.c
> @@ -522,6 +522,9 @@ xfs_bui_item_recover(
> error = xfs_trans_log_finish_bmap_update(tp, budp, bui_type, ip,
> whichfork, bmap->me_startoff, bmap->me_startblock,
> &count, state);
> + if (error == -EFSCORRUPTED)
> + XFS_CORRUPTION_ERROR(__func__, XFS_ERRLEVEL_LOW, mp, bmap,
> + sizeof(*bmap));
> if (error)
> goto err_cancel;
>
> diff --git a/fs/xfs/xfs_extfree_item.c b/fs/xfs/xfs_extfree_item.c
> index 2424230ca2c3..3f8a0713573a 100644
> --- a/fs/xfs/xfs_extfree_item.c
> +++ b/fs/xfs/xfs_extfree_item.c
> @@ -629,6 +629,9 @@ xfs_efi_item_recover(
> error = xfs_trans_free_extent(tp, efdp, extp->ext_start,
> extp->ext_len,
> &XFS_RMAP_OINFO_ANY_OWNER, false);
> + if (error == -EFSCORRUPTED)
> + XFS_CORRUPTION_ERROR(__func__, XFS_ERRLEVEL_LOW, mp,
> + extp, sizeof(*extp));
> if (error)
> goto abort_error;
>
> diff --git a/fs/xfs/xfs_refcount_item.c b/fs/xfs/xfs_refcount_item.c
> index 746f4eda724c..163615285b18 100644
> --- a/fs/xfs/xfs_refcount_item.c
> +++ b/fs/xfs/xfs_refcount_item.c
> @@ -522,6 +522,9 @@ xfs_cui_item_recover(
> error = xfs_trans_log_finish_refcount_update(tp, cudp,
> type, refc->pe_startblock, refc->pe_len,
> &new_fsb, &new_len, &rcur);
> + if (error == -EFSCORRUPTED)
> + XFS_CORRUPTION_ERROR(__func__, XFS_ERRLEVEL_LOW, mp,
> + refc, sizeof(*refc));
> if (error)
> goto abort_error;
>
> diff --git a/fs/xfs/xfs_rmap_item.c b/fs/xfs/xfs_rmap_item.c
> index dc4f0c9f0897..9b91a788722a 100644
> --- a/fs/xfs/xfs_rmap_item.c
> +++ b/fs/xfs/xfs_rmap_item.c
> @@ -578,6 +578,9 @@ xfs_rui_item_recover(
> rmap->me_owner, whichfork,
> rmap->me_startoff, rmap->me_startblock,
> rmap->me_len, state, &rcur);
> + if (error == -EFSCORRUPTED)
> + XFS_CORRUPTION_ERROR(__func__, XFS_ERRLEVEL_LOW, mp,
> + rmap, sizeof(*rmap));
> if (error)
> goto abort_error;
>
--
chandan
next prev parent reply other threads:[~2021-08-06 11:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 7:00 [PATCHSET 0/5] xfs: other stuff for 5.15 Darrick J. Wong
2021-08-05 7:00 ` [PATCH 1/5] xfs: fix silly whitespace problems with kernel libxfs Darrick J. Wong
2021-08-06 5:45 ` Chandan Babu R
2021-08-09 14:51 ` Christoph Hellwig
2021-08-05 7:00 ` [PATCH 2/5] xfs: drop experimental warnings for bigtime and inobtcount Darrick J. Wong
2021-08-06 5:51 ` Chandan Babu R
2021-08-09 14:53 ` Christoph Hellwig
2021-08-05 7:01 ` [PATCH 3/5] xfs: automatic resource cleanup of for_each_perag* Darrick J. Wong
2021-08-06 7:15 ` Chandan Babu R
2021-08-09 15:07 ` Christoph Hellwig
2021-08-05 7:01 ` [PATCH 4/5] xfs: grab active perag ref when reading AG headers Darrick J. Wong
2021-08-06 11:25 ` Chandan Babu R
2021-08-05 7:01 ` [PATCH 5/5] xfs: dump log intent items that cannot be recovered due to corruption Darrick J. Wong
2021-08-06 11:41 ` Chandan Babu R [this message]
2021-08-09 14:55 ` Christoph Hellwig
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=87v94iiyuw.fsf@garuda \
--to=chandanrlinux@gmail.com \
--cc=djwong@kernel.org \
--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