Hello, I have been sometimes annoyed with error message from fossilcons when I did snap -a the messages are something like that:
fossil: diskReadRaw failed: /dev/sdC0/fossil: score 0x006eb183: part=label block 7254403: illegal block address archive(0, 0xfcf3a58b): cannot find block: error reading block 0x006eb183 archWalk 0xfcf3a58b failed; ptr is in 0x22a offset 163 archWalk 0x22a failed; ptr is in 0x220 offset 30 archWalk 0x220 failed; ptr is in 0xf7a offset 0 archWalk 0xf7a failed; ptr is in 0xf79 offset 0 archWalk 0xf79 failed; ptr is in 0xf78 offset 0 archiveBlock 0xf78: error reading block 0x006eb183 fossil: diskReadRaw failed: /dev/sdC0/fossil: score 0x006eb183: part=label block 7254403: illegal block address archive(0, 0xfcf3a58b): cannot find block: error reading block 0x006eb183 archWalk 0xfcf3a58b failed; ptr is in 0x22a offset 163 archWalk 0x22a failed; ptr is in 0x220 offset 30 archWalk 0x220 failed; ptr is in 0xf7a offset 0 archWalk 0xf7a failed; ptr is in 0xf79 offset 0 archWalk 0xf79 failed; ptr is in 0xf78 offset 0 archiveBlock 0xf78: error reading block 0x006eb183 .... The problem is in that these messages repeat endlessly. Is there any way to stop "snap -a"? Isn't it better to fix fossil/disk.c to abort "snap -a" after a few diskReadRaw failures at the same address? Kenji Arisawa
