From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201331] deadlock (XFS?)
Date: Fri, 05 Oct 2018 16:39:55 +0000 [thread overview]
Message-ID: <bug-201331-201763-hP0TZ4Prac@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201331-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201331
--- Comment #10 from edo (edo.rus@gmail.com) ---
> A substripe write will require 4MiB + parity (which IIRC will be another 1024MiB) so a total of 5MiB needs to be Read, modified and written for each undersized write.
I'm pretty sure, md raid can do partial update for chunks.
I just ran 4Kib random write test (fio) on freshly created array with chunk
size 4Kib, after that with chunk size 16Mib - no difference in terms iops on
raid device (observed in fio), iops and transfer speed on raid members
(observed in iostat).
> Your system is not locked up, it's just really slow due the amount of time being spent waiting for IO completion.
No.
Array was filling with good speed (80-250Mib/s, limited by network) several
hours after system startup.
Unexpectedly write stopped (zeros in iostat) and messages "blocked for more
than 120 seconds" arrive. I managed to continue disk filling with hardware
reset only.
Such behavior repeated many times, I tried several kernel versions and kernel
options.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-10-05 23:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 23:14 [Bug 201331] New: deadlock (XFS?) bugzilla-daemon
2018-10-04 23:16 ` [Bug 201331] " 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 [this message]
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-hP0TZ4Prac@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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