Open
Description
lizardfs checkfile reports:
/LIZARD/proxmox/dump/vzdump-qemu-118-2023_03_18-22_08_14.vma.zst:
chunks with 0 copies: 1
chunks with 1 copy: 571
and lizardfs fileinfo reports the missing chunk is:
chunk 117: 0000000002954D8F_00000001 / (id:43339151 ver:1)
copy 1: 192.168.10.103:9423:wd8tb part 1/3 of ec(2,1)
copy 2: 192.168.10.109:9429:fast part 3/3 of ec(2,1)
copy 3: 192.168.10.129:9422:_ part 2/3 of ec(2,1)
chunk 118: 0000000002954D90_00000001 / (id:43339152 ver:1)
no valid copies !!!
chunk 119: 0000000002954D91_00000001 / (id:43339153 ver:1)
copy 1: 192.168.10.103:9423:wd8tb part 2/3 of ec(2,1)
copy 2: 192.168.10.109:9429:fast part 3/3 of ec(2,1)
copy 3: 192.168.10.110:9430:fast part 1/3 of ec(2,1)
I looked on the disk of chunkserver 192.168.10.110 and 192.168.10.109 (since booth had 2 parts of chunk 0000000002954D91_00000001), and found 2 parts of the "missing" chunk on those servers:
/ST16TB/lizardfs/chunks95/chunk_ec_3_of_2_1_0000000002954D90_00000001.mfs
/WD8TB/lizardfs/chunks95/chunk_ec_1_of_2_1_0000000002954D90_00000001.mfs
So, since it's EC(2,1) goal, having 2 of 3 should make the chunk readable, but it's not readable at all, reporting as "no valid copies" by lizardfs fileinfo.
I tried to restart the chunkservers, but it didn't fixed the problem.
Is there any way to make lizardfs "see" those chunk parts and make my file readable?
Metadata
Metadata
Assignees
Labels
No labels