Closed hanyuwei70 closed 4 months ago
seems even w/ RST(kernel 6.7.2) and a fresh mkfs, it still oops: https://fars.ee/N4pJ
seems even w/ RST(kernel 6.7.2) and a fresh mkfs, it still oops: https://fars.ee/N4pJ
Confirmed it's unrelated to this problem. It is due to subpage layer issue.
according to @Rongronggg9 advice, I have tried these
./nullb setup
./nullb create -s 4096 -z 256
./nullb create -s 4096 -z 256
./nullb ls
mkfs.btrfs -s 16k /dev/nullb0
mount /dev/nullb0 /mnt/tmp
btrfs device add /dev/nullb1 /mnt/tmp
btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/tmp
dmesg will have zoned: data raid1 needs raid-stripe-tree
both in 4k & 16k sector size.
seems this bug only occured on real device. Will do any test if someone wish.
Yeah zoned and the raid profiles need RST, but I think the conversion is not checked ahead of time, only in btrfs_load_block_group_*
where it's too late. @naota?
Have already reached to Qu wenruo, he said Johannes is working on it.
Thanks for the report. Fixes are done in kernel, closing.
Device: HC620(HSH721414ALN6M0) I used following command created a RAID1 volume on zoned device w/o RST. (kernel 6.7.0)
and successfully mounted. What's more is that I can read & write some data on it. Then when I begun to BT download, it oops: https://fars.ee/sdDZ Should we forbid convert to RAID1 on zoned device w/o RST in btrfs-progs & kernel ?
edit 1: related dmesg: