From: Jens Axboe <axboe@suse.de>
To: Ric Wheeler <ric@emc.com>
Cc: Nicolas Mailhot <nicolas.mailhot@laposte.net>,
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: Fri, 27 Jan 2006 13:23:08 +0100 [thread overview]
Message-ID: <20060127122308.GH4311@suse.de> (raw)
In-Reply-To: <43DA0E3F.7000507@emc.com>
On Fri, Jan 27 2006, Ric Wheeler wrote:
> Jens Axboe wrote:
>
> >On Thu, Jan 26 2006, Nicolas Mailhot wrote:
> >
> >
> >>
> >>I applied the fua backout patch and the kernel booted beautifully.
> >>Now I guess I need to see if Maxtor released a fixed firmware right ?
> >>(is it possible to change the firmware on a running system ?)
> >>
> >>
> >
> >If you can get an update firmware, it is usually done by booting from
> >DOS floppy and running a special flash utility from there. Can you send
> >me the hdparm -I /dev/sdX output of the problem drive? I think we should
> >just blacklist it for FUA. This bug is so obscure I think it's a better
> >solution than adding a FUA disable module parameter at this point.
> >
> >
> >
> I am not sure that drive vendors support firmware upgrades - the
> downside is that you can produce a nice paper weight if the firmware
> upgrade fails ;-)
Yeah, hence most of them don't put it online. It would be nice to have,
though...
> Also, there are specific versions where I know that you cannot jump from
> firmware version X to version X + 1.
That's unfortunate, too.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-27 12:27 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 [this message]
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=20060127122308.GH4311@suse.de \
--to=axboe@suse.de \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=nicolas.mailhot@laposte.net \
--cc=ric@emc.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.