From: Theodore Ts'o <tytso@mit.edu>
To: Autif Khan <autif.mlist@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Misbehaving SSDs - FTL corruption
Date: Tue, 4 Jun 2013 15:19:36 -0400 [thread overview]
Message-ID: <20130604191936.GT3030@thunk.org> (raw)
In-Reply-To: <CADzUK1JDVJfs_iCe6hk1VFsFmTBCdLtbWCr0aRRa-dGVpxCtLQ@mail.gmail.com>
On Mon, Jun 03, 2013 at 02:02:10PM -0400, Autif Khan wrote:
> We found that a relatively expensive Intel Enterprise SSD works perfectly.
>
> Some relatively inexpensive Crucial, OCZ and Sandisk SSDs do not.
Who knows? You need to ask the SSD vendors; as a file system
developer, all I know is that after the disk lets us know that a
CACHE_FLUSH command has completed, everything is supposed to be on
stable store, including any FTL data.
We have no other way of influencing what the storage device might
decide to do.
> Is there a separate command/syscall to tell the SSD to flush its FTL?
There is no separate SATA command. Just the CACHE_FLUSH SATA command,
and this is what ext4 issues in response to a fsync(2) system call.
It may be that if you wait 30 seconds after the last disk write,
hopefully the crappy SSD has gotten around to writing out all of its
necessary data and metadata. You shouldn't have to do that, but if
you have a crappy drive, you have a crappy drive.
Is there some reason you can use a controlled shutdown most of the
time?
- Ted
prev parent reply other threads:[~2013-06-04 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 18:02 Misbehaving SSDs - FTL corruption Autif Khan
2013-06-04 19:19 ` Theodore Ts'o [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=20130604191936.GT3030@thunk.org \
--to=tytso@mit.edu \
--cc=autif.mlist@gmail.com \
--cc=linux-ext4@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).