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 matter in which biovec that index falls.
A test device generating two-page bios, atop
On Mon, Nov 12, 2018 at 04:53:23PM -0500, Mike Snitzer wrote:
> On Mon, Nov 12 2018 at 11:23am -0500,
> Martin Wilck wrote:
>
> > Hello Lijie,
> >
> > On Thu, 2018-11-08 at 14:09 +0800, lijie wrote:
> > > Add support for Asynchronous Namespace Access as specified in NVMe
> > > 1.3
> > > TP 4004.
On Tue, Nov 13 2018 at 11:18am -0500,
Keith Busch wrote:
> On Mon, Nov 12, 2018 at 04:53:23PM -0500, Mike Snitzer wrote:
> > On Mon, Nov 12 2018 at 11:23am -0500,
> > Martin Wilck wrote:
> >
> > > Hello Lijie,
> > >
> > > On Thu, 2018-11-08 at 14:09 +0800, lijie wrote:
> > > > Add support for
On 13/11/2018 01:23, Andy Grover wrote:
> On 11/9/18 12:21 PM, Andy Grover wrote:
>> As mentioned elsewhere in dm-integrity.txt, creating a new integrity
>> device requires creating a small integrity device on top of the base
>> device that formats the base device, reading the provided data sectors
This is really an alias mismatch, not a minor number mismatch.
Signed-off-by: Martin Wilck
---
multipathd/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/multipathd/main.c b/multipathd/main.c
index 6289718d..0db3 100644
--- a/multipathd/main.c
+++ b/multipathd/
If path reinstantiation is delayed by delay_wait_checks, wait_checks
is counting down, the path fails during the delay phase, and then
comes up again, the wait_check counter starts counting down at the
same value where it previously stopped, which may be very low (even 1).
To avoid that, reset the
Hi Christophe,
Two small fixes, based on my prior submissions which have been
acked by Ben.
Martin
Martin Wilck (2):
multipathd: fix irritating "minor number mismatch" message
multipathd: reset delay_wait_checks counter on failure
multipathd/main.c | 10 +++---
1 file changed, 7 insert
On Tue, Nov 13 2018 at 1:00pm -0500,
Mike Snitzer wrote:
> On Tue, Nov 13 2018 at 11:18am -0500,
> Keith Busch wrote:
>
> > On Mon, Nov 12, 2018 at 04:53:23PM -0500, Mike Snitzer wrote:
> > > On Mon, Nov 12 2018 at 11:23am -0500,
> > > Martin Wilck wrote:
> > >
> > > > Hello Lijie,
> > > >
Merged.
Thanks.
On Tue, Oct 23, 2018 at 3:44 PM Martin Wilck wrote:
> This is v2 of my series from Oct. 10; starting from 7 as the
> other patches have already been merged.
>
> Changes wrt v2:
> 7/10: handle failure of libcheck_init() (Ben). I decided not to
> return PATH_TIMEOUT in th
Merged.
Thanks.
On Fri, Nov 2, 2018 at 1:23 PM Martin Wilck wrote:
> Hi Christophe,
>
> This is v5 of my "checkers overhaul" series. Changed wrt v4
> are 03/22, 11/22, and 21/22. I re-post the whole series to
> avoid confusion.
>
> This series starts with a few minor fixes and then attempts
> an
Merged.
Thanks.
On Fri, Nov 2, 2018 at 1:24 PM Martin Wilck wrote:
> Hi Christophe,
>
> this series, based on top of the recently submitted
> "various multipath-tools patches (v2)" and "checkers overhaul (v3)"
> series, fixes a problem that I recently observed: despite
> ee01e841 "multipathd: ha
On 11/13/18 5:18 PM, Keith Busch wrote:
On Mon, Nov 12, 2018 at 04:53:23PM -0500, Mike Snitzer wrote:
On Mon, Nov 12 2018 at 11:23am -0500,
Martin Wilck wrote:
Hello Lijie,
On Thu, 2018-11-08 at 14:09 +0800, lijie wrote:
Add support for Asynchronous Namespace Access as specified in NVMe
1.3
12 matches
Mail list logo