All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Étienne BERSAC" <etienne.bersac@nonstop.fr>
To: dm-devel@redhat.com
Subject: Re: dm-cache caching network volume
Date: Thu, 20 Jun 2013 11:31:27 +0200	[thread overview]
Message-ID: <1371720687.30405.5.camel@expiron> (raw)
In-Reply-To: <mailman.51.1371657606.18923.dm-devel@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 859 bytes --]

Hi,

Thanks for the reply :-)

I actually uses write-back. Here are the tables :

----8<----
cache_cacher: 0 1024 linear 254:32 2097152
cache_origin: 0 2048 linear 8:0 0
cache: 0 2048 cache 253:3 253:4 253:2 512 1 writeback default 4 sequential_threshold 2147483648 random_threshold 4
cache_metadata: 0 2097152 linear 254:32 0
---->8----

8:0 is /dev/sda, the iSCSI target.
254:32 is /dev/vdc, a virtio volume accessing a LV on a SSD.

The thing is : the cache status properlay state that new blocks in cache
are filled, they are even marked as dirty. Which suggest they are not in
the backing device. But actually, it blocks when iSCSI detects the
network failure.

Can dm-cache handle writes without querying the backing device until it
needs demotion ?

Regards,
-- 
Étienne BERSAC <etienne.bersac@nonstop.fr>
NON STOP Systems

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



       reply	other threads:[~2013-06-20  9:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.51.1371657606.18923.dm-devel@redhat.com>
2013-06-20  9:31 ` Étienne BERSAC [this message]
2013-06-18  9:32 dm-cache caching network volume Étienne BERSAC
2013-06-19  1:23 ` Alex Elsayed
2013-06-19  2:07   ` Alex Elsayed
2013-06-19 16:44     ` Darrick J. Wong
2014-09-09 15:47 ` Joe Thornber

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=1371720687.30405.5.camel@expiron \
    --to=etienne.bersac@nonstop.fr \
    --cc=dm-devel@redhat.com \
    /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.