From: Dan Oglesby <d.oglesby@insightbb.com>
To: Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: Fatal File System Corruption -Software RAID + NFS
Date: Mon, 17 Nov 2003 08:47:17 -0600 [thread overview]
Message-ID: <3FB8DF75.4020802@insightbb.com> (raw)
In-Reply-To: <3FB7CFEB.9080705@g-house.de>
Christian Kujau wrote:
> Steven Poulakos wrote:
> [...]
>
>> Here are snippets of the errors that just repeat over and over...
>>
>> Nov 9 06:47:34 ctdev kernel: hdc: status error: status=0x58 {
>> DriveReady SeekComplete DataRequest }
>> Nov 9 06:47:34 ctdev kernel:
>> Nov 9 06:47:34 ctdev kernel: hdc: status error: status=0x58 {
>> DriveReady SeekCo
>
>
> hardware errors, i'd say :-(
> try to dd / dd_rescue to a working disk, then go on with newest
> reiserfsprogs or /bin/cat...
>
> Christian.
> -
I saw these types of errors on my software RAID-5 array when I first
brought it online. The array is made up of four 20GB hard drives from
four different manufacturers, two drives to an IDE channel. Some of the
drives didn't want to play nice when sharing the IDE channel.
Using hdparm, I found that not all drives were enabling DMA or 32-bit
transfers, so I forced all of the hard drives to run 32-bit with DMA.
This solved the problem.
Another interesting thing I found (while I'm talking about my goofy
array) was that the system performed MUCH better when I disabled write
caching on all of the hard drives.
The filesystem is ReiserFS 3.6, of course.
--Dan
next prev parent reply other threads:[~2003-11-17 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 17:04 Fatal File System Corruption -Software RAID + NFS Steven Poulakos
2003-11-16 19:28 ` Christian Kujau
2003-11-17 14:47 ` Dan Oglesby [this message]
2003-11-17 17:00 ` Steven Poulakos
2003-11-17 20:58 ` Christian Kujau
2003-11-20 19:59 ` Steven Poulakos
2003-11-20 8:20 ` Hans Reiser
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=3FB8DF75.4020802@insightbb.com \
--to=d.oglesby@insightbb.com \
--cc=reiserfs-list@namesys.com \
/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.