My use case doesn't lend itself well to multipathd, so I'm trying to
implement multipathing with device mapper directly.
My table is (kernel 4.19.79):
0 1562378240 multipath 4 queue_if_no_path retain_attached_hw_handler
queue_mode bio 0 1 1 queue-length 0 4 1 253:11 1 253:8 1 253:9 1 253:10 1
On Fri, Nov 22, 2019 at 11:14:15AM +0800, JeffleXu wrote:
> The first question is what's the purpose of data cell? In thin_bio_map(),
> normal bio will be packed as a virtual cell and data cell. I can understand
> that virtual cell is used to prevent discard bio and non-discard bio
> targeting
Hi Linus,
The following changes since commit a99d8080aaf358d5d23581244e5da23b35e340b9:
Linux 5.4-rc6 (2019-11-03 14:07:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
tags/for-5.5/dm-changes
for you to fetch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 22 Nov 2019, Erich Eckner wrote:
Hi,
I have multiple disks with LUKS+integrity created by
cryptsetup luksFormat /dev/sde --key-file /mnt/key/key --integrity
hmac-sha256
which are part of a raid6. Details of the device:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I have multiple disks with LUKS+integrity created by
cryptsetup luksFormat /dev/sde --key-file /mnt/key/key --integrity hmac-sha256
which are part of a raid6. Details of the device:
/dev/mapper/leg0 is active.
type:LUKS2
cipher:
From: Heinz Mauelshagen
[ Upstream commit 74694bcbdf7e28a5ad548cdda9ac56d30be00d13 ]
Sending a check/repair message infrequently leads to -EBUSY instead of
properly identifying an active resync. This occurs because
raid_message() is testing recovery bits in a racy way.
Fix by calling
From: Sweet Tea
[ Upstream commit a00f5276e26636cbf72f24f79831026d2e2868e7 ]
The flakey target is documented to be able to corrupt the Nth byte in
a bio, but does not corrupt byte indices after the first biovec in the
bio. Change the corrupting function to actually corrupt the Nth byte
no
Hi guys,
I have several questions on dm-thin when I'm testing and evaluating IO
performance of dm-thin. I would be grateful if someone could spend a
little time on it.
The first question is what's the purpose of data cell? In
thin_bio_map(), normal bio will be packed as a virtual cell and
From: Sweet Tea
[ Upstream commit a00f5276e26636cbf72f24f79831026d2e2868e7 ]
The flakey target is documented to be able to corrupt the Nth byte in
a bio, but does not corrupt byte indices after the first biovec in the
bio. Change the corrupting function to actually corrupt the Nth byte
no
From: Sweet Tea
[ Upstream commit a00f5276e26636cbf72f24f79831026d2e2868e7 ]
The flakey target is documented to be able to corrupt the Nth byte in
a bio, but does not corrupt byte indices after the first biovec in the
bio. Change the corrupting function to actually corrupt the Nth byte
no
Hi guys,
I have several questions on dm-thin when I'm testing and evaluating IO
performance of dm-thin. I would be grateful if someone could spend a
little time on it.
The first question is what's the purpose of data cell? In
thin_bio_map(), normal bio will be packed as a virtual cell and
11 matches
Mail list logo
