From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 201173] [xfstests xfs/137]: xfs_repair hang when it trying to repair a 500t xfs
Date: Sat, 22 Sep 2018 01:35:25 +0000 [thread overview]
Message-ID: <bug-201173-201763-obG255pYHJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201173-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201173
Eric Sandeen (sandeen@sandeen.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@sandeen.net
Assignee|filesystem_xfs@kernel-bugs. |sandeen@sandeen.net
|kernel.org |
--- Comment #1 from Eric Sandeen (sandeen@sandeen.net) ---
Several hours of debugging later, a simple patch seems to fix this:
diff --git a/repair/prefetch.c b/repair/prefetch.c
index 9571b24..c9a0748 100644
--- a/repair/prefetch.c
+++ b/repair/prefetch.c
@@ -768,8 +768,11 @@ pf_queuing_worker(
* might get stuck on a buffer that has been locked
* and added to the I/O queue but is waiting for
* the thread to be woken.
+ * Start processing as well, in case everything so
+ * far was already prefetched and the queue is empty.
*/
pf_start_io_workers(args);
+ pf_start_processing(args);
sem_wait(&args->ra_count);
}
but it still feels like a slightly odd fix, will give it more thought. The
problem is that if every buffer we tried to read ahead in phase6 was already up
to date, pf_start_io_workers has no effect; there is no io to do, and the
sem_wait waits forever.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-09-22 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 7:30 [Bug 201173] New: [xfstests xfs/137]: xfs_repair hang when it trying to repair a 500t xfs bugzilla-daemon
2018-09-22 1:35 ` bugzilla-daemon [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=bug-201173-201763-obG255pYHJ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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).