From: bryan.coleman@dart.biz
To: linux-ext4@vger.kernel.org, linux-ext4-owner@vger.kernel.org
Subject: Re: ext4 problems with external RAID array via SAS connection
Date: Tue, 8 Feb 2011 08:18:59 -0500 [thread overview]
Message-ID: <OF1BE984CE.39437668-ON85257831.00491D12-85257831.0049261D@dart.biz> (raw)
In-Reply-To: <20110207225436.GG3457@thunk.org>
When I ran fsck after the first bout of failure, it did report a lot of
errors. I do not have a copy of that fsck transcript; however, I have not
yet run fsck since my second attempt. Is there a method of capturing the
transcript that is preferred?
Bryan
From: Ted Ts'o <tytso@mit.edu>
To: bryan.coleman@dart.biz
Cc: linux-ext4@vger.kernel.org
Date: 02/07/2011 05:55 PM
Subject: Re: ext4 problems with external RAID array via SAS
connection
Sent by: linux-ext4-owner@vger.kernel.org
On Mon, Feb 07, 2011 at 01:53:18PM -0500, bryan.coleman@dart.biz wrote:
> I am experiencing problems with an ext4 file system.
>
> At first, the drive seemed to work fine. I was primarily copying things
> to the drive migrating data from another server. After many GBs of
data,
> that seemingly successfully were done being transferred, I started
seeing
> ext4 errors in /var/log/messages. I then unmounted the drive and ran
fsck
> on it (which took multiple hours to run). I then ls'ed around and one
of
> the areas caused the system to again throw ext4 errors.
Did fsck report any errors? Do you have a copy of your fsck
transcript?
The errors you've reported do make me suspicious that there's
something unstable with your hardware...
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-08 13:19 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 [this message]
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
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=OF1BE984CE.39437668-ON85257831.00491D12-85257831.0049261D@dart.biz \
--to=bryan.coleman@dart.biz \
--cc=linux-ext4-owner@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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.