Re: [bcachefs] checksum error probably after switching to crc64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



W dniu 22.09.2016 o 13:14, Marcin Mirosław pisze:
> W dniu 22.09.2016 o 12:58, Marcin Mirosław pisze:
>> Hi!
>> I'm at:
>> commit b7cb7779de9609899fa53f7bab4e3cee69ac1f7e
>> Author: Kent Overstreet <kent.overstreet@xxxxxxxxx>
>> Date:   Wed Sep 21 17:38:38 2016 -0800
>>
>>     bcache: fix an ordering issue in btree_interior_update code
>>
>>     Also a bunch of refactoring
>>
>>
>> Steps:
>> # bcache format --discard  --compression_type=lz4 /dev/system10/bcache
>> (underlaying devices does not support discard)
>> # mount & use fs
>> # echo crc64 > data_checksum
>> # echo crc64 > metadata_checksum
>> # use filesystem
>> After sometime I'm getting:
>> [ 6444.192279] bcache (dm-11): IO error on dm-11 for checksum error
> 
> After some trying to read files dmesg says:
> [ 7651.598498] bcache (dm-11): IO error on dm-11 for checksum error
> [ 7657.066482] bio_checksum_uncompress: 83 callbacks suppressed


And there is another problem. I can read every file (no read error), in
dmesg appear new messages about wrong checksum and this files are putted
into kernel cache.
I can read particular file again and again, no new message about
checksum appears. Then I'm doing echo 3 > ..drop_caches, after this I
reread particular file, I'm getting message about wrong checksum.
Shouldn't be access to such file disallowed?

--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM Kernel]     [Linux Filesystem Development]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux