From: "Darrick J. Wong" <djwong@kernel.org>
To: chandanbabu@kernel.org, djwong@kernel.org
Cc: hch@lst.de, linux-xfs@vger.kernel.org
Subject: [GIT PULL 9/9] xfs: minor fixes to online repair
Date: Tue, 23 Apr 2024 20:35:59 -0700 [thread overview]
Message-ID: <171392953650.1941278.18020942589466688173.stg-ugh@frogsfrogsfrogs> (raw)
In-Reply-To: <20240424033018.GB360940@frogsfrogsfrogs>
Hi Chandan,
Please pull this branch with changes for xfs for 6.10-rc1.
As usual, I did a test-merge with the main upstream branch as of a few
minutes ago, and didn't see any conflicts. Please let me know if you
encounter any problems.
--D
The following changes since commit 4ad350ac58627bfe81f71f43f6738e36b4eb75c6:
xfs: only iget the file once when doing vectored scrub-by-handle (2024-04-23 16:55:18 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git tags/repair-fixes-6.10_2024-04-23
for you to fetch changes up to 5e1c7d0b29f7e05b01e448d2579a469cf3a0d350:
xfs: invalidate dentries for a file before moving it to the orphanage (2024-04-23 16:55:19 -0700)
----------------------------------------------------------------
xfs: minor fixes to online repair [v13.4 9/9]
Here are some miscellaneous bug fixes for the online repair code.
This has been running on the djcloud for months with no problems. Enjoy!
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
----------------------------------------------------------------
Darrick J. Wong (4):
xfs: drop the scrub file's iolock when transaction allocation fails
xfs: fix iunlock calls in xrep_adoption_trans_alloc
xfs: exchange-range for repairs is no longer dynamic
xfs: invalidate dentries for a file before moving it to the orphanage
fs/xfs/scrub/attr_repair.c | 3 +++
fs/xfs/scrub/dir_repair.c | 3 +++
fs/xfs/scrub/nlinks_repair.c | 4 +++-
fs/xfs/scrub/orphanage.c | 49 ++++++++++++++++++-----------------------
fs/xfs/scrub/parent_repair.c | 10 ++++++---
fs/xfs/scrub/rtsummary_repair.c | 10 ++++-----
fs/xfs/scrub/scrub.c | 8 +++----
fs/xfs/scrub/scrub.h | 7 ------
fs/xfs/scrub/symlink_repair.c | 3 +++
fs/xfs/scrub/tempexch.h | 1 -
fs/xfs/scrub/tempfile.c | 24 ++------------------
fs/xfs/scrub/trace.h | 3 ---
12 files changed, 49 insertions(+), 76 deletions(-)
prev parent reply other threads:[~2024-04-24 3:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 3:30 [GIT PULLBOMB v13.4] xfs: directory parent pointers Darrick J. Wong
2024-04-24 3:33 ` [GIT PULL 1/9] xfs: shrink struct xfs_da_args Darrick J. Wong
2024-04-24 3:34 ` [GIT PULL 2/9] xfs: improve extended attribute validation Darrick J. Wong
2024-04-24 3:34 ` [GIT PULL 3/9] xfs: Parent Pointers Darrick J. Wong
2024-04-24 3:34 ` [GIT PULL 4/9] xfs: scrubbing for parent pointers Darrick J. Wong
2024-04-24 3:34 ` [GIT PULL 5/9] xfs: online repair " Darrick J. Wong
2024-04-24 3:35 ` [GIT PULL 6/9] xfs: detect and correct directory tree problems Darrick J. Wong
2024-04-24 3:35 ` [GIT PULL 7/9] xfs: vectorize scrub kernel calls Darrick J. Wong
2024-04-24 3:35 ` [GIT PULL 8/9] xfs: reduce iget overhead in scrub Darrick J. Wong
2024-04-24 3:35 ` Darrick J. Wong [this message]
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=171392953650.1941278.18020942589466688173.stg-ugh@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=hch@lst.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).