On 10/31/14 22:56, Edward Shishkin wrote:
On 10/31/2014 05:37 PM, dE wrote:
Hi!
Hello.
I've encountered a corruption again.
This's what I get when accessing a certain file --
[ 2449.493892] reiser4[gwenview(7968)]: dc_check_checksum
(fs/reiser4/plugin/file/cryptcompress.c:1025)[edward-156]:
WARNING: Bad disk cluster checksum -1008173184, (should be
-1553131906) Fsck?
[ 2449.493898] reiser4[gwenview(7968)]: reiser4_inflate_cluster
(fs/reiser4/plugin/file/cryptcompress.c:1192)[edward-1460]:
WARNING: Inode 3109170: disk cluster 0 looks corrupted
[ 2449.493926] reiser4[gwenview(7968)]: dc_check_checksum
(fs/reiser4/plugin/file/cryptcompress.c:1025)[edward-156]:
WARNING: Bad disk cluster checksum -1008173184, (should be
-1553131906) Fsck?
[ 2449.493929] reiser4[gwenview(7968)]: reiser4_inflate_cluster
(fs/reiser4/plugin/file/cryptcompress.c:1192)[edward-1460]:
WARNING: Inode 3109170: disk cluster 0 looks corrupted
[ 2449.493971] reiser4[gwenview(7968)]: dc_check_checksum
(fs/reiser4/plugin/file/cryptcompress.c:1025)[edward-156]:
WARNING: Bad disk cluster checksum -1008173184, (should be
-1553131906) Fsck?
[ 2449.493974] reiser4[gwenview(7968)]: reiser4_inflate_cluster
(fs/reiser4/plugin/file/cryptcompress.c:1192)[edward-1460]:
WARNING: Inode 3109170: disk cluster 0 looks corrupted
[ 2449.494145] reiser4[gwenview(7968)]: dc_check_checksum
(fs/reiser4/plugin/file/cryptcompress.c:1025)[edward-156]:
WARNING: Bad disk cluster checksum -1008173184, (should be
-1553131906) Fsck?
[ 2449.494157] reiser4[gwenview(7968)]: reiser4_inflate_cluster
(fs/reiser4/plugin/file/cryptcompress.c:1192)[edward-1460]:
WARNING: Inode 3109170: disk cluster 0 looks corrupted
This again happened with the .mozilla/firefox dir.
Anything I can do to report?
Which kernel version?
Is it annoying (reproducible)?
Thanks,
Edward.
3.14.8
It doesn't come up frequently.
Last time I reported this --
http://www.spinics.net/lists/reiserfs-devel/msg03797.html
Which seems to be related.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
