From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: weez@freelists.org, linux-kernel@vger.kernel.org
Subject: Re: DAC960: Bad Data Block Found
Date: Mon, 22 Sep 2003 14:31:18 +0200 [thread overview]
Message-ID: <200309221427.47215.m.c.p@wolk-project.de> (raw)
In-Reply-To: <200309211930.25350.weez@freelists.org>
On Monday 22 September 2003 02:30, John Madden wrote:
Hi John,
> If there's some place better to post this, please let me know. Since the
> DAC960 driver has been orphaned, I haven't heard of anyone stepping up to
> take it over, so I don't know where to go for help other than
> linux-kernel.
well, take a look at: http://www.osdl.org/archive/dmo/DAC960/
I use that driver for some months now w/o any problems at all where 2.4.11
driver version has some problems. I use these controllers:
- Mylex DAC1164P PCI RAID Controller, 64MB cache
- Mylex DAC960PTL1 PCI RAID Controller, 8MB cache
> DAC960#0: Error Condition MEDIUM ERROR on READ:
> DAC960#0: /dev/rd/c0d0: absolute blocks 405095..405102
> DAC960#0: /dev/rd/c0d0p1: relative blocks 405032..405039
> DAC960#0: Error Condition MEDIUM ERROR on READ:
> DAC960#0: /dev/rd/c0d0: absolute blocks 405095..405102
> DAC960#0: /dev/rd/c0d0p1: relative blocks 405032..405039
> DAC960#0: Logical Drive 0 (/dev/rd/c0d0) Bad Data Block Found
> DAC960#0: Logical Drive 0 (/dev/rd/c0d0) Bad Data Block Found
> DAC960#0: Logical Drive 0 (/dev/rd/c0d0) Bad Data Block Found
> Sounds bad, but the drives are still ticking and I haven't noticed any fs
> corruption. How serious is the error? Can it be ignored? Is it time to
> move to another array? Would dropping everything, scrubbing, and
> restoring be sufficient?
hmm, never saw those messages. Already fsck -f'ed? Anyway, those messages
would scare me :)
ciao, Marc
next prev parent reply other threads:[~2003-09-22 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 0:30 John Madden
2003-09-22 12:31 ` Marc-Christian Petersen [this message]
2003-09-22 13:30 ` Alan Cox
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=200309221427.47215.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=linux-kernel@vger.kernel.org \
--cc=weez@freelists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®