From: Edward Shishkin <edward.shishkin@gmail.com>
To: dE <de.techno@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 corruption.
Date: Sat, 01 Nov 2014 13:47:07 +0100 [thread overview]
Message-ID: <5454D64B.1070700@gmail.com> (raw)
In-Reply-To: <5454C129.3020103@gmail.com>
On 11/01/2014 12:16 PM, dE wrote:
> 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
What is the name of the file with Inode 3109170?
You can find out this by the following way:
$ find ~/ -inum 3109170
Also I would ask you to
1) fsck you partition with the option --build-fs;
2) send me the fsck logs;
3) upgrade you kernel to 3.16 or later, or build a new one with the
following patch applied:
http://marc.info/?l=reiserfs-devel&m=141176163530650&w=2
4) let me know, if the problem hasn't gone away.
Thanks,
Edward.
>
> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-01 12:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 16:37 Reiser4 corruption dE
2014-10-31 17:26 ` Edward Shishkin
2014-11-01 11:16 ` dE
2014-11-01 12:47 ` Edward Shishkin [this message]
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=5454D64B.1070700@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=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).