All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: "Ted Ts'o" <tytso@mit.edu>, bryan.coleman@dart.biz
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: ext4 problems with external RAID array via SAS connection
Date: Wed, 09 Feb 2011 14:46:34 -0500	[thread overview]
Message-ID: <4D52EF1A.6060902@redhat.com> (raw)
In-Reply-To: <20110209182823.GC9533@thunk.org>

On 02/09/2011 01:28 PM, Ted Ts'o wrote:
> On Wed, Feb 09, 2011 at 08:43:56AM -0500, bryan.coleman@dart.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


      reply	other threads:[~2011-02-09 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 18:53 ext4 problems with external RAID array via SAS connection bryan.coleman
2011-02-07 22:54 ` Ted Ts'o
2011-02-08 13:18   ` bryan.coleman
2011-02-08 14:50     ` bryan.coleman
2011-02-08 15:19       ` Eric Sandeen
2011-02-08 18:50         ` bryan.coleman
2011-02-08 20:49           ` Eric Sandeen
2011-02-09 13:43             ` bryan.coleman
2011-02-09 18:28               ` Ted Ts'o
2011-02-09 19:46                 ` Ric Wheeler [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=4D52EF1A.6060902@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=bryan.coleman@dart.biz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.