Some errors, tree-related?

Some errors, tree-related?

[mjt]

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?

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

Re: Some errors, tree-related?

[Alex Zarochentsev]

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.

Re: Some errors, tree-related?

[mjt]

On Tue, Jun 29, 2004 at 09:00:39PM +0400, Alex Zarochentsev wrote:
>it shows serious tree corruption. which reiser4 snapshot is on shrike?

2004.06.24, but ported to 2.6.7 by Piotr Neuman, who I added to the CC.

I probably shouldn't have brought this up, using an unsupported version,
but I guess I didn't think of it. If it matters, I'm sorry :P

Why I added you, sikkh, to the CC is that how big changes did you do
for the auto-snapshot to port it?

I guess I'll have to move up to 2.6.7-mm3 as soon as I can launch
a browser. Good thing I didn't destroy my emergency partition yet...

Thanks and I'll keep you posted.

-- 
mjt