All of lore.kernel.org
 help / color / mirror / Atom feed
* Trying to us dmcache with zram block device
@ 2013-12-19  0:31 Daniel Wheeler
  2013-12-20 16:43 ` Joe Thornber
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel Wheeler @ 2013-12-19  0:31 UTC (permalink / raw)
  To: dm-devel

I am trying to use zram for the dmcache meta and dmcache caching device
to cache a local logical volume.

It works just fine if I use logical volumes from a disk as the caching
device, but using a zram block device as the cache sets up properly but
fails to boot a virtual machine on the resulting volume. Interestingly,
I can use zram as a meta cache device without error, but using zram as
the cache itself is when this fails. 

This is how I'm setting up my device map:

0 20758528 cache /dev/zram0 /dev/zram1 /dev/c0v0/vdb 64 1 writethrough mq 6 sequential_threshold 5120 random_threshold 2 migration_threshold 819200

zram0 and zram1 are both 1GB in size so plenty of space here.
I am booting linux 3.11.4 with that version of dmcache.

When I try and boot a VM off of the resulting cache, the VM fails to
write to it's disk (I think), and displays the following error when
booting CentOS 6:

mount: wrong fs type, bad option, bad superblock on /dev/mapper/VM_NAME,
	missing codepage or helper program, or other error
	In some cases useful info is found in syslog - try
	dmesg | tail or so


Kernel Panic - not syncing: Attempting to kill init!
Pid: 1, comm: init Not tainted 2.6.32-279.e16.x86_64 #1
Call Trace:
 [<ffffffff814fd11a>] ? panic+0xa0/0x168
 [<ffffffff81070bd2>] ? do_exit+0x862/0x870
 [<ffffffff8117ca75>] ? fput+0x25/0x30
 [<ffffffff81070c38>] ? do_group_exit+0x58/0xd0
 [<ffffffff81070cc7>] ? sys_exit_group+0x17/0x20
 [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b

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?

How can I test this further?

-Daniel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Trying to us dmcache with zram block device
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Joe Thornber @ 2013-12-20 16:43 UTC (permalink / raw)
  To: device-mapper development

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Trying to us dmcache with zram block device
  2013-12-20 16:43 ` Joe Thornber
@ 2015-06-10  8:00   ` Akira Hayakawa
  0 siblings, 0 replies; 3+ messages in thread
From: Akira Hayakawa @ 2015-06-10  8:00 UTC (permalink / raw)
  To: device-mapper development

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
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-06-10  8:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.