From: Neil Brown <neilb@suse.de>
To: Peter Kieser <peter@kieser.ca>, Terry Hardie <thardie@instartlogic.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Hung RAID5 array with discard
Date: Fri, 23 Oct 2015 16:51:59 +1100 [thread overview]
Message-ID: <87vb9yxhc0.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <5629BE44.8070205@kieser.ca>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
Peter Kieser <peter@kieser.ca> writes:
> On 2015-10-22 9:42 PM, Neil Brown wrote:
>> Peter Kieser <peter@kieser.ca> writes:
>>
>>> FYI I ran into this problem in 3.18.22 when forcing RAID5 TRIM support
>>> w/ raid456.devices_handle_discard_safely on Intel DC S3500 SSDs.
>> Can you please be precise about the problem you experienced.
>> Complete kernel messages are a minimum.
>> Anything interesting that might have been happening at the time might
>> help.
>>
>> Thanks,
>> NeilBrown
>
> Same behaviour as the original poster. Enabled the module knob, then ran
> mkfs.ext4, which starts to do "Discarding device blocks" and then the
> machine hard locked. No kernel messages.
>
Thanks.
The original poster reported a hung-task dump...
When you say "hard locked" - can you still access from another
window/login, or is it totally forzen?
If former, are then any processes in D start? maybe mdXX-raid5?
Can you get /proc/$PID/stack of that process?
If totally frozen - do you have a console? Can you alt-sysrq-W ??
Or have you since rebooted and the problem isn't repeatable?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2015-10-23 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 3:08 Hung RAID5 array with discard Terry Hardie
2015-03-04 21:47 ` Terry Hardie
2015-03-23 2:57 ` NeilBrown
2015-10-22 16:07 ` Peter Kieser
2015-10-23 4:42 ` Neil Brown
2015-10-23 4:57 ` Peter Kieser
2015-10-23 5:51 ` Neil Brown [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=87vb9yxhc0.fsf@notabene.neil.brown.name \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=peter@kieser.ca \
--cc=thardie@instartlogic.com \
/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).