linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John K Luebs <jkluebs@luebsphoto.com>
To: linux-raid@vger.kernel.org
Subject: Write cache / barrier
Date: Sun, 12 Nov 2006 01:00:16 -0500	[thread overview]
Message-ID: <20061112060016.GA15554@kabir> (raw)


I'm using md devices. What I don't understand is how things with the
raid are kept safe when write caching is enabled on the underlying
devices. Forgetting filesystem integrity, if a write access hits
one of the disks and the power goes out, won't the members of the array
be inconsistent without the md layer knowing about it?

For now I am running with write caching turned off.

Also, some drives support write cache flushing and some do not. Does
this make any difference to md?

 Thanks,
   -jkl

                 reply	other threads:[~2006-11-12  6:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20061112060016.GA15554@kabir \
    --to=jkluebs@luebsphoto.com \
    --cc=linux-raid@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).