From: Alex Zarochentsev <zam@namesys.com>
To: "Markus TЖrnqvist" <mjt@nysv.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Some errors, tree-related?
Date: Tue, 29 Jun 2004 21:00:39 +0400 [thread overview]
Message-ID: <20040629170039.GW5080@backtop.namesys.com> (raw)
In-Reply-To: <20040628194741.GG4990@nysv.org>
On Mon, Jun 28, 2004 at 10:47:41PM +0300, Markus Törnqvist wrote:
> Hi
>
> While I was toying around with unrelated stuff, I noticed I got the good
> old jamming problems that I had with some older auto-snapshot, that is,
> apt-get would lock on 93% and tab expansion would as well, then everything
> would lock. Rebooting needs the SysRq trio.
>
> Now I got the behavior again, and noted some stuff in the log that I
> could swear wasn't there when I last had these problems. On the other hand,
> I don't know if they're related. That's why I'm mailing here :)
>
> Jun 28 22:18:53 shrike kernel: reiser4[xmms(3797)]: traverse_tree (fs/reiser4/search.c:747)[nikita-1481]:
> Jun 28 22:18:53 shrike kernel: WARNING: Too many iterations: 1048576
> Jun 28 22:19:15 shrike kernel: reiser4[xmms(3797)]: traverse_tree (fs/reiser4/search.c:747)[nikita-1481]:
> Jun 28 22:19:15 shrike kernel: WARNING: Too many iterations: 2097152
> Jun 28 22:19:46 shrike kernel: reiser4[xmms(3797)]: traverse_tree (fs/reiser4/search.c:747)[nikita-1481]:
> Jun 28 22:19:46 shrike kernel: WARNING: Too many iterations: 4194304
>
> Then I restarted the computer. Bugger me, I can't remember if I restarted
> because of a lock-up there or not, but this I got later:
>
> Jun 28 22:36:21 shrike kernel: reiser4[xmms(3834)]: renew_sibling_link (fs/reiser4/tree_walk.c:441)[nikita-3532]:
> Jun 28 22:36:21 shrike kernel: WARNING: Sibling nodes on the different levels: 1 != 2
>
> [...]
>
> Jun 28 22:38:51 shrike kernel: reiser4[xmms(4068)]: renew_sibling_link (fs/reiser4/tree_walk.c:441)[nikita-3532]:
> Jun 28 22:38:51 shrike kernel: WARNING: Sibling nodes on the different levels: 1 != 2
>
> So, what's up here? Is it related to any known stability issue?
it shows serious tree corruption. which reiser4 snapshot is on shrike?
> I re-mkfs'd my home partition, but did an fsck on the / partition, when it
> was last needed. Could that affect here? Do I _really_ have to mkfs again?
> Or am I barking up the wrong tree? (No pun intended :D)
> Thanks!
>
> --
> mjt
>
--
Alex.
next prev parent reply other threads:[~2004-06-29 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 19:47 Some errors, tree-related? mjt
2004-06-29 17:00 ` Alex Zarochentsev [this message]
2004-06-29 20:04 ` mjt
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=20040629170039.GW5080@backtop.namesys.com \
--to=zam@namesys.com \
--cc=mjt@nysv.org \
--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.