All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Leonardo Santos <heiligerstein@gmail.com>
Cc: dm-devel@redhat.com
Subject: Re: dmcache RAID1 bug?
Date: Mon, 17 Nov 2014 09:46:59 -0500	[thread overview]
Message-ID: <20141117144659.GA29929@redhat.com> (raw)
In-Reply-To: <CAEZ+n-i7kOC3zZzrv5GHbmfuKJ3b1U6COG8DyDW8HjHk9wDf-Q@mail.gmail.com>

On Mon, Nov 17 2014 at  9:24am -0500,
Leonardo Santos <heiligerstein@gmail.com> wrote:

> I'm working in tests for my msc thesis envolving dm_cache module. I'm
> having problems with the following scenario:
> 
> Slowstorage: RAID1 (mdadm) with 4 HDDs;
> - /dev/md/raid1_4ssds

You mean /dev/md/raid1_4hdds ?

> -- /dev/sda
> -- /dev/sdb
> -- /dev/sdc
> -- /dev/sdd
> 
> Faststorage: RAID1 (mdadm) with 4 SSDs
> - /dev/md/raid1_4hdds

And /dev/md/raid1_4ssds here?

> -- /dev/sde
> -- /dev/sdf
> -- /dev/sdg
> -- /dev/sdh
>
> 
> Cachestorage: dm_cache envolving both devices
> - /dev/mapper/dmcache
> -- /dev/md/raid1_4ssds
> -- /dev/md/raid1_4hdds
> 
> Other informations (strange facts):
> In RAID0 it's working very well.
> In a virtual machine (vbox) it's working as well (in this case disks have
> 2GB only for big tests automatization, in production are 160GB SSDs and 2TB
> HDDs);
> 
> Have you seen about this error? Syslog is bellow.

Never seen this before... have you taken care to zero the dm-cache
metadata's superblock (first 512B of the cache metadata device) each
time you've reconfigured the cache device?

Have you tried using the latest lvm2 to create the dm-cache device?

  reply	other threads:[~2014-11-17 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 14:24 dmcache RAID1 bug? Leonardo Santos
2014-11-17 14:46 ` Mike Snitzer [this message]
2014-11-17 18:14   ` Leonardo Santos
2014-11-18 18:18     ` Leonardo Santos
2014-11-19 21:39       ` Leonardo Santos
2014-11-20  4:19         ` Mike Snitzer
2014-11-20 14:04         ` Joe Thornber
2014-11-20 14:10           ` Joe Thornber
2015-02-06 16:33         ` Mike Snitzer

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=20141117144659.GA29929@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=heiligerstein@gmail.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.