On Thu, 3 Aug 2023 19:41:47 +0800 Xiao Ni <xni@xxxxxxxxxx> wrote: > On Thu, Aug 3, 2023 at 3:12 PM Mariusz Tkaczyk > <mariusz.tkaczyk@xxxxxxxxxxxxxxx> wrote: > > > > On Thu, 3 Aug 2023 11:27:57 +0800 > > Xiao Ni <xni@xxxxxxxxxx> 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
