From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: Edward Shishkin <edward.shishkin@gmail.com>,
reiserfs-devel@vger.kernel.org
Subject: Re: reiser4+2.6.38.6 broken?
Date: Mon, 16 May 2011 23:12:51 +0200 [thread overview]
Message-ID: <4520233.UGogC23bit@localhost> (raw)
In-Reply-To: <4DD18A02.3090304@gmail.com>
On Monday 16 May 2011 22:33:06 you wrote:
> On 05/16/2011 10:20 PM, Volker Armin Hemmann wrote:
> > On Monday 16 May 2011 22:16:11 you wrote:
> >> On 05/16/2011 09:55 PM, Volker Armin Hemmann wrote:
> >>> Hi,
> >>>
> >>> I have several r4 partitions, all with cryptcompress.
> >>>
> >>> I tried 2.6.38.x6 a few hours ago - after 3h I looked at dmesg and
> >>> it
> >>> was
> >>> swamped with error messages and tracebacks. Sadly I tried to run
> >>> fsck
> >>> before saving dmesg - and the box froze completely.
> >>>
> >>> I am now back to 2.6.36.4. fsck is running on one of the partitions.
> >>> Meanwhile I see tons of this:
> >>>
> >>> [ 153.379751] reiser4[kuiserver(2649)]: reiser4_inflate_cluster
> >>> (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]:
> >>> [ 153.379756] WARNING: Inode 2975012: disk cluster 27 looks
> >>> corrupted
> >>> [ 163.301372] reiser4[kuiserver(2669)]: dc_check_checksum
> >>> (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]:
> >>> [ 163.301374] WARNING: Bad disk cluster checksum 799645291, (should
> >>> be
> >>> 546616041) Fsck?-2)
>
> [...]
>
> >>> known problem with 2.6.38.X?
> >>
> >> Yes, this is known and old problem.
> >> This is not specific to compression.
> >
> > ok, and how serious?
>
> Serious for what?
> Reiser4 in the current state is not suitable
> for production file servers. For home desktop -
> may be..
>
>
> I am going to let fsck loose as soon as the first
>
> > partition is done. Should I prepare for some major cf?
>
> I _can_ reproduce this problem.
> I don't need any extra-stuff.
and I don't expect you to.
well, fsck worked.
The partition was md1 - which means /var, which also houses portage tree on my
setup and some other vital stuff.
The first run with --build-fs failed with an 'unknown plugin id' error
finishing with an 'operational error'.
Secound run with --build-fs was successfull with only some files in
lost+found. The important stuff seems to be there.
R4 worked for me fine for a long time. But it seems like I should migrate the
more important partitions away from it. How is reisefs doing at the moment?
Glück Auf,
Volker
--
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:[~2011-05-16 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 19:55 reiser4+2.6.38.6 broken? Volker Armin Hemmann
2011-05-16 20:16 ` Edward Shishkin
[not found] ` <1725025.DC6atdjbiy@localhost>
2011-05-16 20:33 ` Edward Shishkin
2011-05-16 21:12 ` Volker Armin Hemmann [this message]
2011-05-16 21:35 ` Edward Shishkin
2011-05-16 21:47 ` Volker Armin Hemmann
2011-05-16 21:57 ` Edward Shishkin
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=4520233.UGogC23bit@localhost \
--to=volkerarmin@googlemail.com \
--cc=edward.shishkin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.