Hi Mariusz Cool. Thanks for reminding me. The test can run successfully. Regards Xiao On Mon, Feb 24, 2025 at 8:35 PM Mariusz <mtkaczyk@xxxxxxxxxxxx> wrote: > > Hi Xiao, > Please try to set systemd env variables for IMSM. I remember that I described it to you once. Please check "test" file for particular variables to set. > > Thanks, > Mariusz > > On Mon, Feb 24, 2025, at 1:24 PM, Xiao Ni wrote: > > Hi all > > I'm trying to fix ddf test errors which we see recently. But I see > this error: "Failed to connect to control socket". I tried with an > imsm array with loop devices and the imsm array also has this problem. > (Note, this problem doesn't appear with real devices which system > supports imsm) > > mdadm -CR /dev/md/imsm -e imsm -n 4 /dev/loop8 /dev/loop9 /dev/loop10 > /dev/loop11 > mdadm -CR /dev/md/vol1 -n 4 -l 10 /dev/loop8 /dev/loop9 /dev/loop10 > /dev/loop11 -z 10000 > mdadm: Creating array inside imsm container /dev/md127 > mdadm: array /dev/md/vol1 started. > mdadm: Failed to connect to control socket. > > [root@ ~]# systemctl status mdmon@md127.service > × mdmon@md127.service - MD Metadata Monitor on md127 > Loaded: loaded (/usr/lib/systemd/system/mdmon@.service; static) > Active: failed (Result: exit-code) since Mon 2025-02-24 05:43:07 > EST; 14s ago > Feb 24 05:43:07 storageqe-59.rhts.eng.pek2.redhat.com systemd[1]: > Started MD Metadata Monitor on md127. > Feb 24 05:43:07 storageqe-59.rhts.eng.pek2.redhat.com mdmon[47066]: > mdmon: Cannot load metadata for md127 > > I used latest mdadm and 6.14.0-rc3+ > > Best Regards > Xiao > >
