From: dE <de.techno@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Reiser4 corruption.
Date: Fri, 31 Oct 2014 22:07:33 +0530 [thread overview]
Message-ID: <5453BACD.8040801@gmail.com> (raw)
Hi!
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?
next reply other threads:[~2014-10-31 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 16:37 dE [this message]
2014-10-31 17:26 ` Reiser4 corruption Edward Shishkin
2014-11-01 11:16 ` dE
2014-11-01 12:47 ` Edward Shishkin
2014-11-01 16:05 ` dE
-- strict thread matches above, loose matches on Subject: below --
2005-06-17 15:26 reiser4 corruption mross
2005-06-17 17:08 ` Edward Shishkin
2005-06-17 17:50 ` mross
2005-06-20 10:35 ` Vladimir Saveliev
2005-05-18 22:12 Reiser4 Corruption Craig Shelley
2004-09-04 18:07 reiser4 corruption Grzegorz Jaśkiewicz
2004-09-04 18:08 ` Grzegorz Jaśkiewicz
2004-09-04 18:23 ` Vince
2004-09-04 18:34 ` Grzegorz Jaśkiewicz
2004-05-22 19:36 dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5453BACD.8040801@gmail.com \
--to=de.techno@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).