linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Feng <fengli@smartx.com>
To: Xiao Ni <xni@redhat.com>
Cc: Song Liu <song@kernel.org>,
	"open list:SOFTWARE RAID (Multiple Disks) SUPPORT" 
	<linux-raid@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] md: allow to set the fail_fast on RAID1/RAID10
Date: Tue, 12 Oct 2021 16:07:22 +0800	[thread overview]
Message-ID: <CAHckoCzzVP7npmU4LWedzD-f1QmkH4K0iLk_=8ptSFXrFfRoDw@mail.gmail.com> (raw)
In-Reply-To: <CALTww28CsJdmVOLFeoHC8FgbHDK78h8Lncsf9fFA0RYXEj=R9A@mail.gmail.com>

Xiao Ni <xni@redhat.com> 于2021年10月12日周二 下午2:58写道：
>
> On Mon, Oct 11, 2021 at 5:42 PM Li Feng <fengli@smartx.com> wrote:
> >
> > Xiao Ni <xni@redhat.com> 于2021年10月11日周一 下午3:49写道：
> > >
> > > Hi all
> > >
> > > Now the per device sysfs interface file state can change failfast. Do
> > > we need a new file for failfast?
> > >
> > > I did a test. The steps are:
> > >
> > > mdadm -CR /dev/md0 -l1 -n2 /dev/sdb /dev/sdc --assume-clean
> > > cd /sys/block/md0/md/dev-sdb
> > > echo failfast > state
> > > cat state
> > > in_sync,failfast
> >
> > This works,  will it be persisted to disk?
> >
>
> mdadm --detail /dev/md0 can show the failfast information. So it
> should be written in superblock.
> But I don't find how md does this. I'm looking at this.
>
Yes, I have tested that it has been persisted, but don't understand who does it.

> Regards
> Xiao
>

  reply	other threads:[~2021-10-12  8:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08  3:22 [PATCH RESEND] md: allow to set the fail_fast on RAID1/RAID10 Li Feng
2021-10-08 23:35 ` Song Liu
2021-10-11  7:49   ` Xiao Ni
2021-10-11  9:42     ` Li Feng
2021-10-12  6:58       ` Xiao Ni
2021-10-12  8:07         ` Li Feng [this message]
2021-10-12  8:17           ` Song Liu
2021-10-12  8:43             ` Li Feng
2021-10-12  8:49               ` Xiao Ni
2021-10-12  9:13                 ` Li Feng
2021-10-13  7:57                   ` Xiao Ni
2021-10-12 17:20                 ` Song Liu

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='CAHckoCzzVP7npmU4LWedzD-f1QmkH4K0iLk_=8ptSFXrFfRoDw@mail.gmail.com' \
    --to=fengli@smartx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=xni@redhat.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;
as well as URLs for NNTP newsgroup(s).