Re: [dm-devel] [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA

On Tue, Apr 03, 2018 at 10:53:29PM +0200, Martin Wilck wrote: > On Tue, 2018-04-03 at 15:31 -0500, Benjamin Marzinski wrote: > > On Tue, Mar 27, 2018 at 11:50:52PM +0200, Martin Wilck wrote: > > > If the hardware handler isn't explicitly set, infer ALUA support > > > from the pp->tpgs attribute.

[dm-devel] [dm:for-next 31/31] drivers/md/dm-zoned-target.c:954:20: error: initialization from incompatible pointer type

tree: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next head: a39e613506eca803cede2cf555d4d1dc485352e7 commit: a39e613506eca803cede2cf555d4d1dc485352e7 [31/31] dm: remove fmode_t argument from .prepare_ioctl hook config: i386-randconfig-x015-201813

Re: [dm-devel] [PATCH v9] dax, dm: introduce ->fs_{claim, release}() dax_device infrastructure

On Tue, Apr 03 2018 at 4:36pm -0400, Dan Williams wrote: > In preparation for allowing filesystems to augment the dev_pagemap > associated with a dax_device, add an ->fs_claim() callback. The > ->fs_claim() callback is leveraged by the device-mapper dax >

Re: [dm-devel] [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA

On Tue, 2018-04-03 at 15:31 -0500, Benjamin Marzinski wrote: > On Tue, Mar 27, 2018 at 11:50:52PM +0200, Martin Wilck wrote: > > If the hardware handler isn't explicitly set, infer ALUA support > > from the pp->tpgs attribute. Likewise, if ALUA is selected, but > > not supported by the hardware,

[dm-devel] [PATCH v9] dax, dm: introduce ->fs_{claim, release}() dax_device infrastructure

In preparation for allowing filesystems to augment the dev_pagemap associated with a dax_device, add an ->fs_claim() callback. The ->fs_claim() callback is leveraged by the device-mapper dax implementation to iterate all member devices in the map and repeat the claim operation across the array.

Re: [dm-devel] [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA

On Tue, Mar 27, 2018 at 11:50:52PM +0200, Martin Wilck wrote: > If the hardware handler isn't explicitly set, infer ALUA support > from the pp->tpgs attribute. Likewise, if ALUA is selected, but > not supported by the hardware, fall back to no hardware handler. Weren't you worried before about

Re: [dm-devel] Recent kernels fail to boot on POWER8 with multipath SCSI

Mike Snitzer writes: > On Fri, Mar 30 2018 at 5:04P -0400, > Michael Ellerman wrote: ... >> Any prospect of getting that patch to Linus before the 4.16 release? Yes >> I realise that's in ~36 hours :) > > Please, see upstream commit

Re: [dm-devel] Recent kernels fail to boot on POWER8 with multipath SCSI

Hi Mike, Paul's AFK so I tried the patch you sent. Mike Snitzer writes: > On Thu, Mar 29 2018 at 4:39am -0400, > Paul Mackerras wrote: >> Since commit 8d47e65948dd ("dm mpath: remove unnecessary NVMe >> branching in favor of scsi_dh checks", 2018-03-05),

Re: [dm-devel] [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios

Dne 3.4.2018 v 11:31 Zdenek Kabelac napsal(a): Dne 3.4.2018 v 06:07 Dennis Yang napsal(a): Hi, Recently we have came across an issue that dm-thin pool will be switched to READ_ONLY mode because dm_pool_alloc_data_block() returns -ENOSPC. AFAIK, this should not happen since alloc_data_block()

Re: [dm-devel] [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios

Dne 3.4.2018 v 06:07 Dennis Yang napsal(a): Hi, Recently we have came across an issue that dm-thin pool will be switched to READ_ONLY mode because dm_pool_alloc_data_block() returns -ENOSPC. AFAIK, this should not happen since alloc_data_block() will check if there is any free space (and commit