From: Vladimir Saveliev <vs@namesys.com>
To: "Łukasz Mierzwa" <prymitive@go2.pl>
Cc: "'reiserfs-list@namesys.com'" <reiserfs-list@namesys.com>
Subject: Re: too many iterations - Reiser 4
Date: Tue, 09 Nov 2004 13:23:55 +0300 [thread overview]
Message-ID: <1099995834.2066.64.camel@tribesman.namesys.com> (raw)
In-Reply-To: <opsg6xa5qewwtuxg@user1.49.priv.jetnet>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
Hello
On Tue, 2004-11-09 at 12:14, Łukasz Mierzwa wrote:
> Dnia Tue, 9 Nov 2004 11:55:28 +0300, Nikita Danilov <nikita@clusterfs.com>
> napisał:
>
> > > > WARNING: Too many iterations: 128 reiser4[ls(30795)]: traverse_tree
> > > > (fs/reiser4/search.c:488)[nikita-1481]:
> > > > WARNING: Too many iterations: 256 reiser4[ls(30795)]: traverse_tree
> > > > (fs/reiser4/search.c:488)[nikita-1481]:
> > > > WARNING: Too many iterations: 512 reiser4[ls(30795)]: traverse_tree
> > > > (fs/reiser4/search.c:488)[nikita-1481]:
> > > > WARNING: Too many iterations: 1024 reiser4[ls(30795)]: traverse_tree
> > > > (fs/reiser4/search.c:488)[nikita-1481]:
>
> I had this few times too when I tried reiser4, first it was when I was
> compiling kernel under 2.6.(6 or 7)-mm with autosnapshots from namesys
> with reiser4 as my / partition. The number of iterations grow all the time
> and the system locked itself after some time (about 10 - 20 minutes), I
> couldn't do much to stop it, not even reboot couse my system just printed
> that it is going to reboot and that's all, seems like it couldn't write
> anything to disk.
> Last time when I tried reiser4 (2.6.9-rc*-mm*) I had no problems with
> compiling kernel but I it happend once or twice, this time it was random,
> just while browsing net.
>
> Łukasz Mierzwa
>
>
would you please try to apply the attached patch?
You should also reiserfsck your reiser4 filesystem.
[-- Attachment #2: reiser4.h.diff --]
[-- Type: text/plain, Size: 469 bytes --]
===== reiser4.h 1.220 vs edited =====
--- 1.220/reiser4.h 2004-11-02 16:01:00 +03:00
+++ edited/reiser4.h 2004-11-09 12:54:07 +03:00
@@ -396,7 +396,7 @@
I have witnessed more than 800 iterations (in 30 thread test) before cbk
finished. --nikita
*/
-#define REISER4_MAX_CBK_ITERATIONS ((unsigned)~0)
+#define REISER4_MAX_CBK_ITERATIONS 500000
/* put a per-inode limit on maximal number of directory entries with identical
keys in hashed directory.
next prev parent reply other threads:[~2004-11-09 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 7:21 too many iterations - Reiser 4 Linzatti Christian
2004-11-09 8:55 ` Nikita Danilov
2004-11-09 9:14 ` Łukasz Mierzwa
2004-11-09 10:23 ` Vladimir Saveliev [this message]
2004-11-09 9:15 ` Vladimir Saveliev
-- strict thread matches above, loose matches on Subject: below --
2004-11-09 10:33 Linzatti Christian
2004-11-12 19:50 christian
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=1099995834.2066.64.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=prymitive@go2.pl \
--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.