* Does multipath require disabled write cache?
@ 2014-07-20 21:20 Spelic
2014-07-21 17:49 ` Mike Snitzer
0 siblings, 1 reply; 2+ messages in thread
From: Spelic @ 2014-07-20 21:20 UTC (permalink / raw)
To: device-mapper development
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).
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.
Thanks for info
S.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Does multipath require disabled write cache?
2014-07-20 21:20 Does multipath require disabled write cache? Spelic
@ 2014-07-21 17:49 ` Mike Snitzer
0 siblings, 0 replies; 2+ messages in thread
From: Mike Snitzer @ 2014-07-21 17:49 UTC (permalink / raw)
To: Spelic; +Cc: device-mapper development
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-07-21 17:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-20 21:20 Does multipath require disabled write cache? Spelic
2014-07-21 17:49 ` Mike Snitzer
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.