From: Mikulas Patocka <mpatocka@redhat.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>, Jan Kara <jack@suse.cz>,
"Kani, Toshi" <toshi.kani@hpe.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Subject: Re: Snapshot target and DAX-capable devices
Date: Thu, 30 Aug 2018 15:47:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.02.1808301545200.30950@file01.intranet.prod.int.rdu2.redhat.com> (raw)
In-Reply-To: <x494lfbabwi.fsf@segfault.boston.devel.redhat.com>
On Thu, 30 Aug 2018, Jeff Moyer wrote:
> Mike Snitzer <snitzer@redhat.com> writes:
>
> > Until we properly add DAX support to dm-snapshot I'm afraid we really do
> > need to tolerate this "regression". Since reality is the original
> > support for snapshot of a DAX DM device never worked in a robust way.
>
> Agreed.
>
> -Jeff
You can't support dax on snapshot - if someone maps a block and the block
needs to be moved, then what?
Mikulas
next prev parent reply other threads:[~2018-08-30 23:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 16:07 Snapshot target and DAX-capable devices Jan Kara
2018-08-27 16:43 ` Kani, Toshi
2018-08-28 7:50 ` Jan Kara
2018-08-28 17:56 ` Mike Snitzer
2018-08-28 22:38 ` Kani, Toshi
2018-08-30 9:30 ` Jan Kara
2018-08-30 18:49 ` Mike Snitzer
2018-08-30 19:32 ` Jeff Moyer
2018-08-30 19:47 ` Mikulas Patocka [this message]
2018-08-30 19:53 ` Jeff Moyer
2018-08-30 23:38 ` Dave Chinner
2018-08-31 9:42 ` Jan Kara
2018-09-05 1:25 ` Dave Chinner
2018-12-12 16:11 ` Huaisheng Ye
2018-12-12 16:12 ` Christoph Hellwig
2018-12-12 17:50 ` Mike Snitzer
2018-12-12 19:49 ` Kani, Toshi
2018-12-12 21:15 ` Theodore Y. Ts'o
2018-12-12 22:43 ` Mike Snitzer
2018-12-14 4:11 ` [dm-devel] " Theodore Y. Ts'o
2018-12-14 8:24 ` [External] " Huaisheng HS1 Ye
2018-12-18 19:49 ` Mike Snitzer
2018-08-30 19:44 ` Mikulas Patocka
2018-08-31 10:01 ` Jan Kara
2018-08-30 22:55 ` Dave Chinner
2018-08-31 9:54 ` Jan Kara
2018-08-30 19:17 ` [dm-devel] " Jeff Moyer
2018-08-31 9:14 ` Jan Kara
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=alpine.LRH.2.02.1808301545200.30950@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=snitzer@redhat.com \
--cc=toshi.kani@hpe.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 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).