All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Étienne BERSAC" <etienne.bersac@nonstop.fr>
To: dm-devel@redhat.com
Subject: dm-cache caching network volume
Date: Tue, 18 Jun 2013 11:32:52 +0200	[thread overview]
Message-ID: <1371547972.6128.8.camel@expiron> (raw)


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

Hi,

I'm testing dm-cache for using a local SSD as a cache for a network
volume. My goal is to test dm-cache behaviour when network is down.

The device is shared through iSCSI. The first test is filling a huge
file with dd from /dev/zero. So, this is sequential access. While dd is
running, i remove the tun iface from the bridge on the host. iSCSI
properly detects the network failure.

I expected dm-cache to continue filling dirty blocks, even if the
network device is blocking. But it doesn't. The status shows that dirty
blocks count stays the same. dd is blocking.

I'm wondering if there is some cache desactivation due to
sequential_threshold. But increasing sequential_threshold did not help.
Where does dm-cache blocks ?

Is it possible to have dm-cache "bufferize" blocks for network
failures ?

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-18  9:32 UTC|newest]

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

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=1371547972.6128.8.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.