Re: LVM2 test breakage

[Yu Kuai <yukuai1@huaweicloud.com>]

Hi,

在 2025/05/19 18:45, Zdenek Kabelac 写道:
> Dne 19. 05. 25 v 12:10 Mikulas Patocka napsal(a):
>> On Mon, 19 May 2025, Yu Kuai wrote:
>>
>>> Hi,
>>>
>>> 在 2025/05/19 9:11, Yu Kuai 写道:
>>>> Hi,
>>>>
>>>> 在 2025/05/17 0:00, Mikulas Patocka 写道:
>>>>> Hi
>>>>>
>>>>> The commit e879a0d9cb086c8e52ce6c04e5bfa63825a6213c breaks the test
>>>>> shell/lvcreate-large-raid.sh in the lvm2 testsuite.
>>>>>
>>>>> The breakage is caused by removing the line "read_bio->bi_opf = op |
>>>>> do_sync;"
>>>>>
>>> Do I need some special setup to run this test? I got following
>>> result in my VM, and I don't understand why it failed.
>>>
>>> Ask Zdenek Kabelac - he is expert in the testsuite.
>>>
>>> Mikulas
> 
> 
> Hi
> 
> 
> Lvm2 test suite is creating 'virtual' disk setup - it usually tries 
> first build something with 'brd' - if this device is 'in-use' it 
> fallback to create some files in LVM_TEST_DIR.
> 
> This dir however must allow creation of device - by default nowdays  
> /dev/shm & /tmp are mounted with  'nodev' mount option.
> 
> So a dir which does allow dev creation must be passed to the test - so 
> either remount dir without 'nodev' or set LVM_TEST_DIR to the filesystem 
> which allows creation of devices.

Yes, I know that, and I set LVM_TEST_DIR to a new mounted nvme, as use
can see in the attached log:

[ 0:02.335] ## DF_H:    /dev/nvme0n1     98G   64K   93G   1% /mnt/test

> 
> In 'lvm2/test'   run  'make help'  to see all possible settings - useful 
> one could be LVM_TEST_AUX_TRACE  to expose shell traces from test 
> internals - helps with debugging...
The log do have shell trace, I think, it stoped here, I just don't know
why :(

[ 0:01.709] ## - /root/lvm2/test/shell/lvcreate-large-raid.sh:31
[ 0:01.710] ## 1 STACKTRACE() called from 
/root/lvm2/test/shell/lvcreate-large-raid.sh:31

Thanks,
Kuai