mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Wilck <martin.wilck@suse.com>
To: Kenta Akagi <k@mgml.me>, Xiao Ni <xiao@kernel.org>,
	Li Nan <magiclinan@didiglobal.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	song@kernel.org, 	yukuai@fnnas.com, shli@fb.com,
	mtkaczyk@kernel.org
Subject: Re: [PATCH v6 1/2] md: Don't set MD_BROKEN for RAID1 and RAID10 when using FailFast
Date: Wed, 23 Sep 2026 10:29:06 +0200	[thread overview]
Message-ID: <adf11fcf1435728f98b4f94c1821d86b83866c14.camel@suse.com> (raw)
In-Reply-To: <010601a0cc7347e3-ff9a517e-b03b-4de5-bd38-93b664f3425c-000000@ap-northeast-1.amazonses.com>

Hi Kenta,

On Wed, 2026-09-23 at 04:08 +0000, Kenta Akagi wrote:
> 
> 
> Hi Martin,
> 
> I have not given up on it, but I have not managed to post v7 yet.
> I still think failfast should be usable even in setups like that.
> 
> It has been a while, but I intend to resume work on it.

My thinking is that, in the fastfail case, code to prevent total
failure could be placed in the end-IO code code path, e.g. by
attempting a retry directly from the md layer when the last rdev fails,
instead of setting failing the device. But I haven't thought it
through.

Thanks
Martin

-- 
Dr. Martin Wilck <mwilck@suse.com>
SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg,
Germany
Geschäftsführer: Stefan Gaiser, Jochen Jaser, Abhinav Puri (HRB
36809,AG Nürnberg)

  reply	other threads:[~2026-09-23  8:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 14:40 [PATCH v6 0/2] Don't set MD_BROKEN on failfast bio failure Kenta Akagi
2026-01-05 14:40 ` [PATCH v6 1/2] md: Don't set MD_BROKEN for RAID1 and RAID10 when using FailFast Kenta Akagi
2026-01-06  2:57   ` Li Nan
2026-01-06  7:59     ` Xiao Ni
2026-01-06  9:11       ` Li Nan
2026-01-06  9:25         ` Xiao Ni
2026-01-06 11:14           ` Li Nan
2026-01-06 12:30     ` Kenta Akagi
2026-01-07  2:09       ` Li Nan
2026-01-07  3:35       ` Xiao Ni
2026-01-07  6:43         ` Kenta Akagi
2026-01-16  2:04         ` Kenta Akagi
2026-09-17 13:58           ` Martin Wilck
2026-09-23  4:08             ` Kenta Akagi
2026-09-23  8:29               ` Martin Wilck [this message]
2026-09-24 16:27                 ` Kenta Akagi
2026-09-24 17:59                   ` Martin Wilck
2026-01-05 14:40 ` [PATCH v6 2/2] md/raid10: fix failfast read error not rescheduled Kenta Akagi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=adf11fcf1435728f98b4f94c1821d86b83866c14.camel@suse.com \
    --to=martin.wilck@suse.com \
    --cc=k@mgml.me \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=magiclinan@didiglobal.com \
    --cc=mtkaczyk@kernel.org \
    --cc=shli@fb.com \
    --cc=song@kernel.org \
    --cc=xiao@kernel.org \
    --cc=yukuai@fnnas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®