[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68713dca-20a9-c498-bb89-af5430c0672d@huaweicloud.com>
Date: Thu, 25 Jan 2024 10:36:59 +0800
From: Yu Kuai <yukuai1@...weicloud.com>
To: Song Liu <song@...nel.org>, Yu Kuai <yukuai1@...weicloud.com>
Cc: mpatocka@...hat.com, dm-devel@...ts.linux.dev, snitzer@...nel.org,
agk@...hat.com, xni@...hat.com, jbrassow@....redhat.com, neilb@...e.de,
heinzm@...hat.com, shli@...com, akpm@...l.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, yi.zhang@...wei.com, yangerkun@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH v2 00/11] dm-raid: fix v6.7 regressions
Hi,
在 2024/01/25 9:51, Song Liu 写道:
> Hmm.. maybe it is caused by different .config? Attached is the
> output from the test and the config file I used.
Looks like your test differs from mine here:
| [ 0:16.663] aux wait_for_sync $vg $lv
| [ 0:17.002] #lvconvert-raid-reshape-linear_to_raid6-single-type.sh:67+
aux wait_for_sync LVMTEST2056vg LV
| [ 0:17.002] LVMTEST2056vg/LV (raid5_ls) in-sync, but 'a' characters in
health status
| [ 0:17.200] LVMTEST2056vg/LV (raid5_ls) in-sync, but 'a' characters in
health status
Mine:
[ 0:08.875] #lvconvert-raid-reshape-linear_to_raid6-single-type.sh:67+
aux wait_for_sync LVMTEST2826329vg LV
[ 0:08.876] LVMTEST2826329vg/LV (raid5_ls) is in-sync 0 98304 raid
raid5_ls 4 AAAA 32768/32768 idle 0 0 -
[ 0:08.940] fsck -fn "$DM_DEV_DIR/$vg/$lv"
[ 0:08.943] #lvconvert-raid-reshape-linear_to_raid6-single-type.sh:68+
fsck -fn /mnt/test/LVMTEST2826329.RgRdke29n8/dev/LVMTEST2826329vg/LV
However, the we all enabled dm and raid related config, I have no clue
yet. :(
Thanks,
Kuai
Powered by blists - more mailing lists