Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1433243 > unrolled thread
| Started by | Toshi Kani <toshi.kani@hpe.com> |
|---|---|
| First post | 2016-06-28 21:40 +0200 |
| Last post | 2016-06-28 21:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH 0/2] Support DAX for device-mapper dm-linear devices Toshi Kani <toshi.kani@hpe.com> - 2016-06-28 21:40 +0200
Re: [PATCH 0/2] fix dm-snap for dax "Kani, Toshimitsu" <toshi.kani@hpe.com> - 2016-06-28 21:50 +0200
| From | Toshi Kani <toshi.kani@hpe.com> |
|---|---|
| Date | 2016-06-28 21:40 +0200 |
| Subject | [PATCH 0/2] Support DAX for device-mapper dm-linear devices |
| Message-ID | <rP71w-2K4-25@gated-at.bofh.it> |
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(-)
[toc] | [next] | [standalone]
| From | "Kani, Toshimitsu" <toshi.kani@hpe.com> |
|---|---|
| Date | 2016-06-28 21:50 +0200 |
| Subject | Re: [PATCH 0/2] fix dm-snap for dax |
| Message-ID | <rP7bb-2NB-5@gated-at.bofh.it> |
| In reply to | #1433243 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web