Re: dm-cache - should origin device and cache be identical when quiescent?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: dm-cache - should origin device and cache be identical when quiescent?
From: Joe Thornber <thornber@xxxxxxxxxx>
Date: Fri, 23 Jan 2015 11:21:51 +0000
In-reply-to: <CALq2s-HVaHBGY1BkBkgxmcef36H4KjTGAQoLNJk3JCE5qqe1sA@mail.gmail.com>
Mail-followup-to: device-mapper development <dm-devel@xxxxxxxxxx>
References: <CALq2s-HVaHBGY1BkBkgxmcef36H4KjTGAQoLNJk3JCE5qqe1sA@mail.gmail.com>
Reply-to: device-mapper development <dm-devel@xxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)

On Fri, Jan 23, 2015 at 12:14:33PM +1000, Alex Sudakar wrote:
>   dmsetup create cache --table '0 1843200 cache /dev/vdb3 /dev/vdb2
> /dev/vdb1 64 1 writeback default 0

Use 'writethrough' rather than 'writeback'.

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

References:
- dm-cache - should origin device and cache be identical when quiescent?
  - From: Alex Sudakar

Prev by Date: A couple of questions related to dm-thin in linux-3.19-rc5
Next by Date: Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
Previous by thread: dm-cache - should origin device and cache be identical when quiescent?
Next by thread: A couple of questions related to dm-thin in linux-3.19-rc5
Index(es):
- Date
- Thread

[Index of Archives] [DM Crypt] [Fedora Desktop] [ATA RAID] [Fedora Marketing] [Fedora Packaging] [Fedora SELinux] [Yosemite Discussion] [KDE Users] [Fedora Docs]

Powered by Linux