From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 201331] New: deadlock (XFS?)
Date: Thu, 04 Oct 2018 23:14:51 +0000 [thread overview]
Message-ID: <bug-201331-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201331
Bug ID: 201331
Summary: deadlock (XFS?)
Product: File System
Version: 2.5
Kernel Version: 4.18.12
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: edo.rus@gmail.com
Regression: No
Created attachment 278927
--> https://bugzilla.kernel.org/attachment.cgi?id=278927&action=edit
dmesg output
I've set up new server with ten of 10Tb disks.
Main volume is XFS over RAID6 (created with mdadm).
For now fs is filling with data. After several hours of uptime disk IO freezes
with such messages in log:
[ 5679.900329] INFO: task tar:18235 blocked for more than 120 seconds.
[ 5679.900404] Not tainted 4.18.12 #2
...
[ 5679.904044] INFO: task kworker/u24:3:18307 blocked for more than 120
seconds.
[ 5679.904137] Not tainted 4.18.12 #2
and so on.
I'm unsure, but it seems to be XFS-related.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2018-10-05 6:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 23:14 bugzilla-daemon [this message]
2018-10-04 23:16 ` [Bug 201331] deadlock (XFS?) bugzilla-daemon
2018-10-04 23:17 ` bugzilla-daemon
2018-10-04 23:18 ` bugzilla-daemon
2018-10-04 23:25 ` bugzilla-daemon
2018-10-05 1:06 ` bugzilla-daemon
2018-10-05 8:20 ` bugzilla-daemon
2018-10-05 9:08 ` bugzilla-daemon
2018-10-05 9:11 ` bugzilla-daemon
2018-10-05 9:18 ` bugzilla-daemon
2018-10-05 10:15 ` bugzilla-daemon
2018-10-05 16:39 ` bugzilla-daemon
2018-10-05 17:09 ` bugzilla-daemon
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-201331-201763@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