All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
To: Jens Axboe <axboe@suse.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
	Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: regarding bug #5914 - fs corruption on SATA
Date: Tue, 31 Jan 2006 23:54:09 +0100	[thread overview]
Message-ID: <43DFEA91.9090405@laposte.net> (raw)
In-Reply-To: <20060131084736.GP4215@suse.de>

Jens Axboe a écrit :

> Sounds like it works, if you saw the errors so quickly.

Well you know while I was testing broken kernels the problem was more to 
keep the finger on reset on boot and act before too much damage was done 
rather than waiting for hard-to-spot symptoms. Seems root on md1+lvm is 
very good to flush fua problems.

> Just trying to
> be absolutely sure, if you could check for the "w/ FUA" prints not being
> there now it would confirm that the blacklist does its job.

The patched kernel ran for a day without hiccups. I've attached its 
demesg to the redhat bug - you can check if it's ok for you (yes I've 
rebooted since and no it was not a ata problem - just you 
run-of-the-mill rawhide xorg freeze)

https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=123941

Regards,

-- 
Nicolas Mailhot

  reply	other threads:[~2006-01-31 23:00 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 [this message]
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     ` regarding bug #5914 - fs corruption on SATA Soeren Sonnenburg

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=43DFEA91.9090405@laposte.net \
    --to=nicolas.mailhot@laposte.net \
    --cc=axboe@suse.de \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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.