From: Kinga Tanska <kinga.tanska@linux.intel.com>
To: Xiao Ni <xni@redhat.com>
Cc: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: The imsm regression tests fail
Date: Thu, 31 Aug 2023 11:25:03 +0200 [thread overview]
Message-ID: <20230831112411.0000561e@intel.linux.com> (raw)
In-Reply-To: <CALTww28VmeQXbTn4ONxE4Y9M3rR6OkQhcE6AMUkw_5LSOTPuLg@mail.gmail.com>
On Thu, 3 Aug 2023 19:41:47 +0800
Xiao Ni <xni@redhat.com> wrote:
> On Thu, Aug 3, 2023 at 3:12 PM Mariusz Tkaczyk
> <mariusz.tkaczyk@linux.intel.com> wrote:
> >
> > On Thu, 3 Aug 2023 11:27:57 +0800
> > Xiao Ni <xni@redhat.com> wrote:
> >
> > > Hi Mariusz
> > >
> > > Now most imsm regression tests fail.
> > >
> > > +++ /home/mdadm/mdadm --quiet --create --run /dev/md/vol0
> > > --auto=md --level=0 --size=5120 --chunk=64 --raid-disks=3
> > > /dev/loop0 /dev/loop1 /dev/loop2 --auto=yes
> > > +++ rv=0
> > > +++ case $* in
> > > +++ cat /var/tmp/stderr
> > > mdadm: timeout waiting for /dev/md/vol0
> > >
> > > +++ echo '**Fatal**: Array member /dev/md/vol0 not found'
> > > **Fatal**: Array member /dev/md/vol0 not found
> > >
> > > Could you have a look at this problem?
> > >
> > > Best Regards
> > > Xiao
> > >
> >
> > Hi Xiao,
> > Please provide (I guess it is md126):
> > # mdadm -D --export /dev/md126
> >
> > If there is no MD_DEVNAME property then udev has no content to make
> > the link.
> >
> > Do you have this one applied?
> > https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=ef6236da232e968dcf08b486178cd20d5ea97e2a
> >
> > Thanks,
> > Mariusz
> >
>
> Hi Mariusz
>
> I re-complied the codes and the failure disappeared. Thanks for your
> feedback.
>
> Regards
> Xiao
>
Hi,
I've met similar issue, there was a timeout while creating a
container.
I've realized that I have been used IMSM_DEVNAME_AS_SERIAL flag while
creating a container, but I haven't exported this flag globally. Udev
has not this flag set while "mdadm --detail --no-devices --export
/dev/md127" was called, and, from some reason, mdadm do not fill
MD_DEVNAME property in this case, and, as a result, do not create a
link.
I'm looking for a root cause in mdadm now, why MD_DEVNAME property is
not set always. If you have used this flag to test, it may be the
same issue.
Regards,
Kinga Tanska
prev parent reply other threads:[~2023-08-31 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 3:27 The imsm regression tests fail Xiao Ni
2023-08-03 7:04 ` Mariusz Tkaczyk
2023-08-03 11:41 ` Xiao Ni
2023-08-31 9:25 ` Kinga Tanska [this message]
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=20230831112411.0000561e@intel.linux.com \
--to=kinga.tanska@linux.intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--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).