From: Jens Axboe <axboe@suse.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Tejun Heo <htejun@gmail.com>,
Nicolas.Mailhot@laposte.net, Jeff Garzik <jgarzik@pobox.com>,
Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: regarding bug #5914 - fs corruption on SATA
Date: Thu, 26 Jan 2006 15:27:14 +0100 [thread overview]
Message-ID: <20060126142714.GA4290@suse.de> (raw)
In-Reply-To: <58cb370e0601260611y67abe723w6085ab30e7e6274e@mail.gmail.com>
On Thu, Jan 26 2006, Bartlomiej Zolnierkiewicz wrote:
> On 1/26/06, Jens Axboe <axboe@suse.de> wrote:
> > On Thu, Jan 26 2006, Tejun Heo wrote:
> > > Hello, Nicolas. Hello, all.
> > >
> > > Nicolas, I'm probably the guy who broke your filesystem. :-p This FUA
> > > (forced-unit-access)thing made into the mainline lately, and it seems
> > > that your drive is reporting FUA support but doesn't really do it
> > > properly when it's asked to.
> >
> > It's strange. I have 3 out of 4 drives in a box here reporting FUA
> > capability, and I have now tested all three of them both with plain FUA
> > writes and NCQ FUA tagged writes. I used data integrity verifying
> > writes, and the data is sound as well. fs likewise, I used ext3 mounted
> > with barriers enabled.
>
> You are just lucky ;-). There are drives out there having buggy NCQ
> support. Windows driver for Sil have them listed in .inf file, you can also
Oh yeah, I'm very well aware of NCQ firmware issues. Interesting about
the Sil inf file having them listed, I started a blacklist myself for
NCQ and I'll be sure to look at theirs!
> find discussions on various internet forums about problems (including
> data corruption) with these drives and controllers supporting NCQ.
But that's a seperate story, it's just plain FUA that is the case here.
> However there is official firmware update so hopefully it can be fixed
> (unfortunately we still need to blacklist buggy firmware revisions).
>
> I wouldn't be surprised if there is similar situation with FUA support.
> Does anybody know if Windows use FUA?
Actually I'm a little surprised, honestly. It's a pretty simple feature.
It's not like NCQ where I can understand that bugs can creap into the
firmware (although some are so buggy it's unbelivable).
--
Jens Axboe
next prev parent reply other threads:[~2006-01-26 14:35 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 [this message]
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=20060126142714.GA4290@suse.de \
--to=axboe@suse.de \
--cc=Nicolas.Mailhot@laposte.net \
--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 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).