From: Akira Hayakawa <ruby.wktk@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Trying to us dmcache with zram block device
Date: Wed, 10 Jun 2015 17:00:30 +0900 [thread overview]
Message-ID: <5577EE9E.8020807@gmail.com> (raw)
In-Reply-To: <20131220164319.GB15982@debian>
Hi,
Sorry to interrupt.
A similar issue is reported with dm-writeboost and zram cache device.
The bug there is that metadata read failed in initialization.
Do you have some advance on this issue?
I am wondering if it's device-mapper that misbehaves.
- Akira
On 2013/12/21 1:43, Joe Thornber wrote:
> On Wed, Dec 18, 2013 at 04:31:09PM -0800, Daniel Wheeler wrote:
>> Can you think of any reason that zram cannot be a cache for dmcache devices?
>>
>> If this is a bug, does it reside in dmcache or in zram?
>
> Hmm, not sure what's going on here. We'll try and set up a similar test.
>
> - Joe
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
prev parent reply other threads:[~2015-06-10 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 0:31 Trying to us dmcache with zram block device Daniel Wheeler
2013-12-20 16:43 ` Joe Thornber
2015-06-10 8:00 ` Akira Hayakawa [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=5577EE9E.8020807@gmail.com \
--to=ruby.wktk@gmail.com \
--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.