From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun <htejun@gmail.com>
Cc: Jens Axboe <axboe@suse.de>,
Nicolas.Mailhot@LaPoste.net, linux-ide@vger.kernel.org
Subject: Re: [akpm@osdl.org: Re: 2.6.16 eating filesystems]
Date: Thu, 26 Jan 2006 12:05:19 -0500 [thread overview]
Message-ID: <43D9014F.8090004@pobox.com> (raw)
In-Reply-To: <43D8FDA5.3000701@gmail.com>
Tejun wrote:
> Anyways, it's clear that we need to do something to prevent data
> corruption on barrier failures. Nicolas's case is just too scary. It
> should warn and turn off barrier, not corrupt whole fs. Maybe we should
> turn off libata FUA support until this issue is resolved?
If the problem can't be fixed in the short term, that's what we'll have
to do. Add a 'fua' module parameter or something.
Jeff
next prev parent reply other threads:[~2006-01-26 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060125185320.GL14225@havoc.gtf.org>
[not found] ` <43D8373B.1070802@gmail.com>
[not found] ` <20060126080544.GH4212@suse.de>
2006-01-26 16:49 ` [akpm@osdl.org: Re: 2.6.16 eating filesystems] Tejun
2006-01-26 17:05 ` Jeff Garzik [this message]
2006-01-26 18:52 ` Jens Axboe
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=43D9014F.8090004@pobox.com \
--to=jgarzik@pobox.com \
--cc=Nicolas.Mailhot@LaPoste.net \
--cc=axboe@suse.de \
--cc=htejun@gmail.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).