linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kani, Toshimitsu" <toshi.kani-ZPxbGqLxI0U@public.gmane.org>
To: "snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org"
	<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH 0/2] fix dm-snap for dax
Date: Tue, 28 Jun 2016 19:43:26 +0000	[thread overview]
Message-ID: <1467143000.3504.431.camel@hpe.com> (raw)
In-Reply-To: <1467142636-21094-1-git-send-email-toshi.kani-ZPxbGqLxI0U@public.gmane.org>

Sorry, subject line should be "[PATCH 0/2] fix dm-snap for dax"
-Toshi

On Tue, 2016-06-28 at 13:37 -0600, Toshi Kani wrote:
> I noticed that dm-snap reloads DM table of target mapped-device, which
> fails for dax-capable device after dax support is added.  Ideally,
> adding dax support to dm-snap solves the issue, but it cannot be done
> easily.  This patch-set allows dm-snap to work with dax-capable target
> devices when bio-based operation is used.
> 
> dax operation is unsupported with dm-snap, such that:
>  a) After snapshot is taken, mount with dax option to a target device
>     or a snapshot device fails.  They can be mounted without dax.
>  b) After snapshot is taken to a dax-mounted target device, any writes 
>     to the target device fails (EIO).
> 
> b) can be protected by changing lvcreate to fail when snapshot is
> requested to a dax-mounted target device. 
> 
> - Patch 1 solves an error when lvremove is made to a snapshot device.
> - Patch 2 solves an error when lvcreate --snapshot is made to a dax-
>   capable device.
> 
> ---
> Toshi Kani (2):
>  1/2 dm: update table type check for dax
>  2/2 dm snap: add fake origin_direct_access
> 
> ---
>  drivers/md/dm-ioctl.c | 11 ++++++++++-
>  drivers/md/dm-snap.c  |  8 ++++++++
>  2 files changed, 18 insertions(+), 1 deletion(-)
> _______________________________________________
> Linux-nvdimm mailing list
> Linux-nvdimm@lists.01.org
> https://lists.01.org/mailman/listinfo/linux-nvdimm
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

      parent reply	other threads:[~2016-06-28 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 19:37 [PATCH 0/2] Support DAX for device-mapper dm-linear devices Toshi Kani
     [not found] ` <1467142636-21094-1-git-send-email-toshi.kani-ZPxbGqLxI0U@public.gmane.org>
2016-06-28 19:37   ` [PATCH 1/2] dm: update table type check for dax Toshi Kani
     [not found]     ` <1467142636-21094-2-git-send-email-toshi.kani-ZPxbGqLxI0U@public.gmane.org>
2016-06-28 20:07       ` Mike Snitzer
     [not found]         ` <20160628200714.GC8300-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-28 20:23           ` Kani, Toshimitsu
     [not found]             ` <1467145398.3504.439.camel-ZPxbGqLxI0U@public.gmane.org>
2016-06-29  0:40               ` Mike Snitzer
     [not found]                 ` <20160629004049.GA9721-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-29 15:19                   ` Kani, Toshimitsu
2016-06-28 20:33       ` kbuild test robot
2016-06-28 19:37   ` [PATCH 2/2] dm snap: add fake origin_direct_access Toshi Kani
2016-06-28 20:27     ` kbuild test robot
2016-06-28 19:43   ` Kani, Toshimitsu [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=1467143000.3504.431.camel@hpe.com \
    --to=toshi.kani-zpxbgqlxi0u@public.gmane.org \
    --cc=agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).