linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Xiao Ni <xni@redhat.com>
Cc: linux-raid@vger.kernel.org, jes@trained-monkey.org,
	song@kernel.org, yukuai1@huaweicloud.com, ncroxon@redhat.com,
	colyli@suse.de
Subject: Re: [PATCH 2/5] tests/00createnames enhance
Date: Mon, 22 Apr 2024 12:15:18 +0200	[thread overview]
Message-ID: <20240422121518.00003ecb@linux.intel.com> (raw)
In-Reply-To: <CALTww28CNBYHrfScPgh9XCr932VeNw=WJFeXiqQM26XwE=DaKQ@mail.gmail.com>

On Mon, 22 Apr 2024 14:57:16 +0800
Xiao Ni <xni@redhat.com> wrote:

> On Fri, Apr 19, 2024 at 5:47 PM Mariusz Tkaczyk
> <mariusz.tkaczyk@linux.intel.com> wrote:
> >
> > On Thu, 18 Apr 2024 18:23:18 +0800
> > Xiao Ni <xni@redhat.com> wrote:
> >  
> > > +     local is_super1="$(mdadm -D --export $DEVNODE_NAME | grep
> > > MD_METADATA=1.2)"  
> >
> > You can also limit this test to super-1.2 it may depend on config, so we can
> > specify metadata directly in create command (if it is not specified).  
> 
> Could you explain more? I don't catch you here.

Default metadata could be customized. At first glance, I thought
that you added this because we metadata is not specified so I checked:
	if [[ -z "$NAME" ]]; then
		mdadm -CR "$DEVNAME" -l0 -n 1 $dev0 --force
	else
		mdadm -CR "$DEVNAME" --name="$NAME" --metadata=1.2 -l0 -n 1
	$dev0 --force
        fi


It seems that I forgot to add metadata specifier in first create command. If
you have different metadata than 1.2 you can add --metadata=1.2 and then:

> > > +     local is_super1="$(mdadm -D --export $DEVNODE_NAME | grep
> > > MD_METADATA=1.2)" 

won't be needed. Do I miss something?

Thanks,
Mariusz

  reply	other threads:[~2024-04-22 10:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 10:23 [PATCH RFC 0/5] mdadm tests fix and enhance Xiao Ni
2024-04-18 10:23 ` [PATCH 1/5] tests/test enhance Xiao Ni
2024-04-19  7:16   ` Mateusz Kusiak
2024-04-19  7:30     ` Mateusz Kusiak
2024-04-21  2:46       ` Xiao Ni
2024-04-18 10:23 ` [PATCH 2/5] tests/00createnames enhance Xiao Ni
2024-04-19  7:20   ` Mariusz Tkaczyk
2024-04-22  6:56     ` Xiao Ni
2024-04-22  7:23       ` Mariusz Tkaczyk
2024-04-19  9:47   ` Mariusz Tkaczyk
2024-04-22  6:57     ` Xiao Ni
2024-04-22 10:15       ` Mariusz Tkaczyk [this message]
2024-04-22 13:31         ` Xiao Ni
2024-04-18 10:23 ` [PATCH 3/5] tests/01r5fail enhance Xiao Ni
2024-04-19  9:57   ` Mariusz Tkaczyk
2024-05-08  8:35   ` Mariusz Tkaczyk
2024-04-18 10:23 ` [PATCH 4/5] tests/01r5integ.broken Xiao Ni
2024-05-08  8:36   ` Mariusz Tkaczyk
2024-04-18 10:23 ` [PATCH 5/5] tests/01raid6integ.broken can be removed Xiao Ni
2024-04-19 10:05   ` Mariusz Tkaczyk
2024-04-19 15:57     ` Song Liu
2024-04-22 13:54       ` Xiao Ni
2024-05-08  8:37         ` Mariusz Tkaczyk

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=20240422121518.00003ecb@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=colyli@suse.de \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=ncroxon@redhat.com \
    --cc=song@kernel.org \
    --cc=xni@redhat.com \
    --cc=yukuai1@huaweicloud.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).