linux-ext4 - Re: ext4 problems with external RAID array via SAS connection

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4D52EF1A.6060902@redhat.com>
Date:	Wed, 09 Feb 2011 14:46:34 -0500
From:	Ric Wheeler <rwheeler@...hat.com>
To:	"Ted Ts'o" <tytso@....edu>, bryan.coleman@...t.biz
CC:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: ext4 problems with external RAID array via SAS connection

On 02/09/2011 01:28 PM, Ted Ts'o wrote:
> On Wed, Feb 09, 2011 at 08:43:56AM -0500, bryan.coleman@...t.biz wrote:
>> The fsck said it completed successfully.  I kicked off fsck again just to
>> make sure and it reported clean.  So I mounted the drive and ls'd around
>> and it started reporting errors.  "ls: cannot access 40: Input/output
>> error"  Note: 40 is a directory.
> Well, we'd need to look at the kernel messages, but the Input/output
> error strongly suggests that there are, well, I/O errors talking to
> your storage array.  Which again suggests hardware problems, or device
> driver bugs, or both.
>
> 						- Ted

I think that you might want to start to test with a simplified storage config. 
Try keep the RAID card in the loop, but using a simpler RAID scheme (single 
drive? RAID0 or RAID1) and see if the issue persists.

Ric

--
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