Re: [dm-devel] [PATCH] persistent-data: fix bug about btree of updating internal node's minima key in btree_split_beneath.

Look forward to your test result. The scene I found with problem as follows: note: 1. key size: 8; 2. value size: 8; 3. max_entries=252; 4. one level btree's root is A. operations: 1. A's info: nr_entries=252 keys:127-378 2. insert 379 to btree

[dm-devel] [PATCH v5] dm: add unstriped target

From: Scott Bauer [Preamble: I started with v3 and then folded in v4 and then refactored. I've only compile tested... ran out of time to test today. Please review and let me know what you think, if you're OK with this I'll get it staged for 4.16. Thanks!] This device

Re: [dm-devel] [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device

On Mon, Dec 18 2017 at 2:32pm -0500, Mike Snitzer wrote: > On Mon, Dec 18 2017 at 1:52pm -0500, > Scott Bauer wrote: > > > > > > > +config DM_UN_STRIPE > > > > + tristate "Transpose IO to individual drives on a raid device" > > > > +

Re: [dm-devel] [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device

On Mon, Dec 18 2017 at 1:52pm -0500, Scott Bauer wrote: > > > > +config DM_UN_STRIPE > > > + tristate "Transpose IO to individual drives on a raid device" > > > + depends on BLK_DEV_DM > > > + ---help--- > > > + Enable this feature if you with to

Re: [dm-devel] [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device

On 12/18/2017 09:28 AM, Scott Bauer wrote: > This device mapper module remaps and unstripes IO so it lands > solely on a single drive in a RAID 0/dm-stripe target. > In a 4 drive RAID 0 the mapper exposes 1/4th of the LBA range > as a virtual drive. Each IO to that virtual drive will land on >

[dm-devel] [PATCH v4 0/2] dm unstriped: add new target

This is a quick rework of the new "unstripe" target (undoes a striped/raid0 mapping) v3 patch series authored by Scott Bauer addressing some points discussed here and more. Addressed: - rename target to "unstriped" - enhance constructor header - add more consistency checks to constructor imposing

[dm-devel] [PATCH v4 2/2] dm unstriped: add documentation for target

--- Documentation/device-mapper/dm-unstripe.txt | 130 1 file changed, 130 insertions(+) create mode 100644 Documentation/device-mapper/dm-unstripe.txt diff --git a/Documentation/device-mapper/dm-unstripe.txt b/Documentation/device-mapper/dm-unstripe.txt new file

[dm-devel] [PATCH v4 1/2] dm unstriped: the target

Signed-off-by: Heinz Mauelshagen --- drivers/md/Kconfig | 11 +++ drivers/md/Makefile | 1 + drivers/md/dm-unstripe.c | 233 +++ 3 files changed, 245 insertions(+) create mode 100644 drivers/md/dm-unstripe.c diff

Re: [dm-devel] [PATCH] persistent-data: fix bug about btree of updating internal node's minima key in btree_split_beneath.

On Mon, Dec 18, 2017 at 05:13:08PM +, Joe Thornber wrote: > Hi Monty, > > On Mon, Dec 18, 2017 at 04:27:58PM -0500, monty wrote: > > Subject: [PATCH] persistent-data: fix bug about btree of updating internal > > node's minima > > key in btree_split_beneath. > > > > fix bug about

Re: [dm-devel] [PATCH] persistent-data: fix bug about btree of updating internal node's minima key in btree_split_beneath.

Hi Monty, On Mon, Dec 18, 2017 at 04:27:58PM -0500, monty wrote: > Subject: [PATCH] persistent-data: fix bug about btree of updating internal > node's minima > key in btree_split_beneath. > > fix bug about btree_split_beneath func, this bug may cause a key had > been inserted to btree, but

Re: [dm-devel] [PATCH] multipath-tools: Makefile: Respect standard toolchain related envvars

On Wed, 2017-12-13 at 14:28 +0100, Xose Vazquez Perez wrote: > On 12/12/2017 04:28 PM, Bart Van Assche wrote: > > On Thu, 2017-11-30 at 00:23 +0100, Thomas Deutschmann wrote: > > > The Makefile overrides standard envvars that control the > > > toolchain flags. > > > This patch should set things

[dm-devel] [PATCH] persistent-data: fix bug about btree of updating internal node's minima key in btree_split_beneath.

Signed-off-by: monty --- drivers/md/persistent-data/dm-btree.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/md/persistent-data/dm-btree.c b/drivers/md/persistent-data/dm-btree.c index f21ce6a..25ce5ec 100644 ---

Re: [dm-devel] [PATCH 2/2] libmultipath: don't update path queueing on reload

On Wed, 2017-12-13 at 12:08 -0600, Benjamin Marzinski wrote: > With the fix to the features handling code, the multipath device > should > already be reloaded with the correct value for queue_if_no_path, so > there's no need to go reset it immediately afterwards. > > Cc: Martin Wilck