linux-ext4 - Re: mpt2sas + raid10 goes boom

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 09 Apr 2013 12:11:13 +0200
From:	Matthias Prager <linux@...thiasprager.de>
To:	Baruch Even <baruch@...en.org>,
	linux-scsi <linux-scsi@...r.kernel.org>
CC:	linux-raid <linux-raid@...r.kernel.org>,
	linux-ext4@...r.kernel.org, Chris Dunlop <chris@...he.net.au>,
	Matthias Prager <linux@...thiasprager.de>
Subject: Re: mpt2sas + raid10 goes boom

Thanks for your insights Baruch.
The crc count did not increase any further - so this was probably just
small oddity (was zero before when the write-same issue already
happened). The real issue however does persist. I found a way to
reliably trigger the log messages. Using a program called checksum over
a photo share (which does a lot of reads and one write per file). With
that in place I switched to the 3.4.38 kernel, with which I'm unable to
trigger the problem. I will leave the system at that for now, and try to
reproduce it on my testing machine to see, whether
  c8dc9c6 md: raid1,10: Handle REQ_WRITE_SAME flag in write bios
works for me.

If c8dc9c6 does the trick, it would still be interesting to know why and
how this triggered i/o errors, the strange log message from lsi and
'Resets Between Cmd Acceptance and Completion' as one of the drives
says. Would that mean the driver/firmware from lsi is issuing or passing
on commands to the drive which it does not understand or can't process?

---
Matthias
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html