linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Evan Jones <evanj@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Intel SSD data loss: Any possible way this is user / software error?
Date: Sun, 15 Aug 2010 11:18:59 -0500	[thread overview]
Message-ID: <4C681373.9090409@redhat.com> (raw)
In-Reply-To: <AD482FB5-0A56-43F2-BB70-8F218657DCE0@MIT.EDU>

Evan Jones wrote:
> On Aug 13, 2010, at 7:57 , Eric Sandeen wrote:
>> Just out of curiosity, what do you see when the write cache is on?
>> Seems counter-intuitive that it'd work better, but talking w/
>> Ric Wheeler, he was curious... maybe Intel didn't test with the
>> write cache off?
> 
> Data loss is much easier to trigger with the write cache on. It happens
> to me on the first try. With the write cache off, I've only been able to
> get it to occur with large writes (64 kB or larger), and only about once
> every 3 times.

Ok, so working as expected then, really.

...

>> Also, would you be willing to publish the test you're using?
> 
> The programs I have been using are here (but see below):
> 
> http://people.csail.mit.edu/evanj/hg/index.cgi/hstore/file/tip/logging/minlogcrash.c
> 
> http://people.csail.mit.edu/evanj/hg/index.cgi/hstore/file/tip/logging/logfilecrashserver.cc

Cool, thanks for publishing all that info, a few people have done 
power loss testing, always interesting to see what's been put together.

I'll take a closer look at some point...

-Eric

      reply	other threads:[~2010-08-15 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 21:02 Intel SSD data loss: Any possible way this is user / software error? Evan Jones
2010-08-13 11:57 ` Eric Sandeen
2010-08-13 16:07   ` Evan Jones
2010-08-15 16:18     ` Eric Sandeen [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=4C681373.9090409@redhat.com \
    --to=sandeen@redhat.com \
    --cc=evanj@mit.edu \
    --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).