All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Schroeder" <prq@Safe-mail.net>
To: linux-btrfs@vger.kernel.org
Subject: How to know whether disks "handle flush requests correctly"
Date: Fri, 6 May 2011 05:13:11 -0400	[thread overview]
Message-ID: <N1-HLiSwHA1HL@Safe-mail.net> (raw)

The btrfs wiki Main Page warns that "it is currently possible to corrupt
a filesystem irrecoverably if your machine crashes or loses power on disks
that don't handle flush requests correctly."

How do you know if this applies to your drives? Is there a way to test it,
or a model list, or are newer SATA drives (magnetic, not SSDs) always ok?
Does it depend on the controller? (I have a SiI 3114, latest BIOS.)

I would also be using btrfs on top of dm-crypt (with the latest release
kernel). Some kernel versions ago, the message that write barriers aren't
supported disappeared; can I assume the device mapper / dm-crypt is not a
problem with regards to flushing?

Paul

             reply	other threads:[~2011-05-06  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  9:13 Paul Schroeder [this message]
2011-05-06 13:10 ` How to know whether disks "handle flush requests correctly" Josef Bacik
2011-05-06 13:48   ` Chris Mason

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=N1-HLiSwHA1HL@Safe-mail.net \
    --to=prq@safe-mail.net \
    --cc=linux-btrfs@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 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.