From: "Łukasz Mierzwa" <prymitive@pcserwis.net>
To: Jussi Judin <jjudin+reiser@iki.fi>,
"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: [BUG] nikita-1481, nikita-717 and nikita-373 here and there
Date: Fri, 23 Jun 2006 12:11:28 +0200 [thread overview]
Message-ID: <op.tblfxehpd4os1z@localhost> (raw)
In-Reply-To: <449B2D1D.9000507@iki.fi>
Dnia Fri, 23 Jun 2006 01:51:57 +0200, Jussi Judin <jjudin+reiser@iki.fi>
napisa³:
> I was using some Debian patched 2.6.16 kernel and reiser4-2.6.16-1 patch
> for that and suddenly got the error messages attached. The java program
> in those error messages is doing a huge amount of writes all the time
> and probably in many threads at the same time.
>
I'm using 2.6.16 + reiser4-2.6.16-4 patch and I just got those errors
while running emerge --sync on gentoo:
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 128
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 256
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 512
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 1024
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 2048
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 4096
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 8192
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 16384
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 32768
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 65536
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 131072
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]:
WARNING: Too many iterations: 262144
reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:723)[nikita-373]:
WARNING: reiser-2018: Too many iterations. Tree corrupted, or (less
likely) starvation occurring.: level: 5, lock_level: 1, stop_level: 1
lock_mode: write, bias: exact
After running fsck.reiser4 --fix the only corruption found was error in
amount of free space
next prev parent reply other threads:[~2006-06-23 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 23:51 [BUG] nikita-1481, nikita-717 and nikita-373 here and there Jussi Judin
2006-06-23 10:11 ` Łukasz Mierzwa [this message]
2006-08-01 20:39 ` Craig Shelley
2006-08-02 14:58 ` Alexander Zarochentsev
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=op.tblfxehpd4os1z@localhost \
--to=prymitive@pcserwis.net \
--cc=jjudin+reiser@iki.fi \
--cc=reiserfs-list@namesys.com \
/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.