From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Resident Boxholder <resid@boxho.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem: IDE data corruption with VIA chipsets
Date: Sat, 13 Sep 2003 18:04:15 +0100 [thread overview]
Message-ID: <1063472654.8519.2.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <3F62A18A.4090901@boxho.com>
On Sad, 2003-09-13 at 05:48, Resident Boxholder wrote:
> Sep 12 06:27:22 heinous logger: rundig htdig start incremental
> # errors are on md3 which is /var, and htdig was indexing
> # /var/www/www.some.com's--hdc: ST340016A, ATA DISK drive
> Sep 12 06:31:33 heinous kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Sep 12 06:31:33 heinous kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=67028386, sector=67028382
Again the drive is reporing that it failed.
> hdc: dma_int: error=0x40 {UnrecoverableError}, LBAsect=57970918, sector=57970918
> end_request: I/O error, dev hdc, sector 57970918
> Buffer I/O error on device md3, logical block 6101
> lost page write due to I/O error on md3
> journal-601, buffer write failed
Finally reiserfs got into a state where it couldnt recover so it pulled
things down rather than cause further damage. I'm not aware of paticular
problems with modern seagate drives.
prev parent reply other threads:[~2003-09-13 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 18:20 Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others Eric Bickle
2003-09-11 18:43 ` Alan Cox
2003-09-12 8:14 ` Rogier Wolff
2003-09-12 10:44 ` Alan Cox
2003-09-13 4:48 ` Problem: IDE data corruption with VIA chipsets Resident Boxholder
2003-09-13 17:04 ` Alan Cox [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=1063472654.8519.2.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=resid@boxho.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 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®