From: Soeren Sonnenburg <kernel@nn7.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: David Greaves <david@dgreaves.com>, Tejun Heo <htejun@gmail.com>,
Nicolas.Mailhot@LaPoste.net, Jens Axboe <axboe@suse.de>,
Linux-ide <linux-ide@vger.kernel.org>,
Christopher Smith <csmith@nighthawkrad.net>,
Erik Slagter <erik@slagter.name>,
hahn@physics.mcmaster.ca, mlaks@verizon.net,
mlaks@verizononline.net
Subject: Re: regarding bug #5914 - fs corruption on SATA
Date: Thu, 26 Jan 2006 18:20:15 +0100 [thread overview]
Message-ID: <1138296016.9413.72.camel@localhost> (raw)
In-Reply-To: <43D8FF9A.4020805@pobox.com>
On Thu, 2006-01-26 at 11:58 -0500, Jeff Garzik wrote:
> David Greaves wrote:
> > Have a look for subjects such as
> > Problems with multiple Promise SATA150 TX4 cards
>
> This is almost certainly either a power or PCI bus/slot issue.
So you mean the freeze I am observing when I copy files from the sata
disk to some
ieee1394 device (they are sharing interrupt 16)
16: 430796 IO-APIC-level ide2, ide3, libata, ohci1394
leading to lots of output as...
ata2: translated ATA stat/err 0x51/0c to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x0c { DriveStatusError }
could be a cause of just that ?
> > Possible libata/sata/Asus problem (was Re: Need to upgrade to latest
> > stable mdadm version?)
>
> Highly likely to be a motherboard/BIOS issue related to properly tuning
> and timing the hardware.
>
> HOWEVER, libata can help (via Tejun's recent patches) by properly
> handling the error when throw to us by hardware.
So it could help in the first case but also with this: I can freeze the
system bei hdparm -y /dev/sda ... will this patch also help in that
case ?
Soeren.
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
prev parent reply other threads:[~2006-01-26 17:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 5:50 regarding bug #5914 - fs corruption on SATA Tejun Heo
2006-01-26 5:51 ` Tejun Heo
2006-01-26 9:14 ` Nicolas Mailhot
2006-01-26 9:21 ` Jens Axboe
2006-01-26 10:01 ` Nicolas Mailhot
[not found] ` <5840.192.54.193.25.1138269692.squirrel@rousalka.dyndns.org>
2006-01-26 21:04 ` Nicolas Mailhot
2006-01-27 8:13 ` Jens Axboe
2006-01-27 8:53 ` Nicolas Mailhot
2006-01-27 9:10 ` Jens Axboe
2006-01-27 9:20 ` Jens Axboe
2006-01-27 9:27 ` Nicolas Mailhot
2006-01-27 9:46 ` Bartlomiej Zolnierkiewicz
2006-01-27 9:50 ` Jens Axboe
2006-01-27 19:37 ` Nicolas Mailhot
2006-01-27 23:54 ` Nicolas Mailhot
2006-01-30 15:08 ` Jens Axboe
2006-01-30 23:33 ` Nicolas Mailhot
2006-01-31 7:26 ` Jens Axboe
2006-01-31 8:39 ` Nicolas Mailhot
2006-01-31 8:47 ` Jens Axboe
2006-01-31 22:54 ` Nicolas Mailhot
2006-01-27 12:12 ` Ric Wheeler
2006-01-27 12:23 ` Jens Axboe
2006-01-26 9:18 ` Jens Axboe
2006-01-26 14:11 ` Bartlomiej Zolnierkiewicz
2006-01-26 14:27 ` Jens Axboe
2006-01-26 16:41 ` David Greaves
2006-01-26 16:58 ` Jeff Garzik
2006-01-26 17:15 ` David Greaves
2006-02-07 18:35 ` SMART on SATA reporting errors? (was Re: regarding bug #5914 - fs corruption on SATA) David Greaves
2006-02-07 19:30 ` Jeff Garzik
2006-02-08 7:21 ` David Greaves
2006-01-26 17:20 ` Soeren Sonnenburg [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=1138296016.9413.72.camel@localhost \
--to=kernel@nn7.de \
--cc=Nicolas.Mailhot@LaPoste.net \
--cc=axboe@suse.de \
--cc=csmith@nighthawkrad.net \
--cc=david@dgreaves.com \
--cc=erik@slagter.name \
--cc=hahn@physics.mcmaster.ca \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlaks@verizon.net \
--cc=mlaks@verizononline.net \
/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;
as well as URLs for NNTP newsgroup(s).