All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Spelic <spelic@shiftmail.org>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Does multipath require disabled write cache?
Date: Mon, 21 Jul 2014 13:49:39 -0400	[thread overview]
Message-ID: <20140721174939.GA31622@redhat.com> (raw)
In-Reply-To: <53CC3287.3010708@shiftmail.org>

On Sun, Jul 20 2014 at  5:20pm -0400,
Spelic <spelic@shiftmail.org> wrote:

> Hello all,
> I am wondering if multipath requires a disabled write cache at the
> remote disks.
> We have some external SAS disks, for which the connection is flaky
> and sometimes is lost and then they are detected again. Multipath
> seems perfect for this situation.
> However, when the disks are lost, I suppose resets are issued, which
> might clear the write cache so that data located there might not be
> committed (true? well at least on power loss this is true).

You should disable both the controller cache and disk caches if they are
volatile.  Filesystems will issue flushes (and DM will handle those
flushes) but until those flushes return successfully the associated
outstanding data is not considered on permanent storage.

> It would be great if multipath would issue a flush every N  writes,
> and then remember the last N  writes and resubmit them when the path
> is reestablished, so that there is again chance to flush them to
> stable storage. (similar to DRBD epochs) However I don't know if
> this smart mechanism is implemented.

It isn't implemented.

      reply	other threads:[~2014-07-21 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20 21:20 Does multipath require disabled write cache? Spelic
2014-07-21 17:49 ` Mike Snitzer [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=20140721174939.GA31622@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=spelic@shiftmail.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.