From: Heinz Mauelshagen <heinzm@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-cache: dirty state of blocks in writethrough mode
Date: Fri, 26 Jul 2013 13:14:01 +0200 [thread overview]
Message-ID: <51F259F9.1090107@redhat.com> (raw)
In-Reply-To: <20130726024546.GA8707@gmail.com>
On 07/26/2013 04:45 AM, Kumar amit mehta wrote:
> On Thu, Jul 25, 2013 at 12:45:31PM +0200, Heinz Mauelshagen wrote:
>> You can set up a mirrored metadata device to be resilient against
>> SSD failures.
> Okay
>
>> Plus you can take metadata snapshots at arbitrary points in time;
>> see the targets kernel documentation in thin-provisioning.txt for this
>> and the recent thin_dump support metadata snapshots in the rawhide
>> device-mapper-persistent-data package.
>>
> So these feature is already upstream and also in fedora 20, but not in
> Red Hat 6.4 yet ?
No, it's planned for RHEL7.
>
>> Either is subject to future LVM2 support and isn't supported as yet.
> So, if LVM2 doesn't support it as of now, Any idea if EVMS or any other
> volume Managers consume these features?
None that I'm aware of.
Use dmsetup for early testing.
We'll support it in LVM2 later in the year.
Heinz
>
> !!amit
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2013-07-26 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 6:44 dm-cache: dirty state of blocks in writethrough mode Vijarnia, Anil
2013-07-23 13:26 ` Heinz Mauelshagen
2013-07-24 10:24 ` Kumar amit mehta
2013-07-24 17:05 ` Heinz Mauelshagen
2013-07-24 13:02 ` Kumar amit mehta
2013-07-25 10:45 ` Heinz Mauelshagen
2013-07-26 2:45 ` Kumar amit mehta
2013-07-26 11:14 ` Heinz Mauelshagen [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=51F259F9.1090107@redhat.com \
--to=heinzm@redhat.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.