linux-kernel - Re: mvsas with 3.1 (mdraid+xfs locked up, single drive w/xfs not locked up)

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 17 Jan 2012 11:55:41 +0800
From:	Brad Campbell <brad@...rfbargle.com>
To:	thomas@...llstrom.ca
CC:	linux-kernel@...r.kernel.org,
	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	ayan@...vell.com, andy yan <andyysj@...il.com>,
	linux-raid <linux-raid@...r.kernel.org>
Subject: Re: mvsas with 3.1 (mdraid+xfs locked up, single drive w/xfs not
 locked up)

On 17/01/12 11:00, Thomas Fjellstrom wrote:
>
> Here's something interesting though, I just tried writing to the one disk on
> the card that isn't part of the mdraid raid5 volume. It is fine. I can read
> from it and write to it. So something to do with mdraid, or the XFS filesystem
> (or both) is causing a bad interaction with the card itself.

Try doing IO to multiple drives simultaneously. I had a SIL card that would corrupt data when used 
in RAID, but not single drive IO tests. I could make it fail by doing multiple dd/cp/md5sum to two 
drives simultaneously.

Do yourself a favour. Whack it on fleabay and sell it to a Windows user, then get something 
supported. Leave enough scatter around that people thinking of buying a card with that Marvell 
chipset will stay clear.

Regards,
Brad
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/