All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: reiserfs-list@namesys.com
Subject: [reiser4 errors] does this ever happen? / too many iterations
Date: Wed, 08 Sep 2004 17:30:34 +0200	[thread overview]
Message-ID: <413F259A.5010501@fujitsu-siemens.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

Hi list,

I got the following errors during a file system benchmark on an x86_64 
system yesterday. I was running 2.6.9-rc1-mm2 with WLI's fix 
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0409.0/0027.html
applied.

First I get a bunch of these:

reiser4[sync(32230)]:
capture_reiser4_inodes (reiser4/page_cache.c:611)[vs-1689]:
      WARNING: does this ever happen? nr_to_write = -1558

Later it gets even worse:

reiser4[bonnie++(32563)]:
traverse_tree (reiser4/search.c:755)[nikita-1481]:
     WARNING: Too many iterations: 128

The # of iterations then goes all the way up to 1073741824,
the bonnie++ process hangs in an infinite loop, and the file system is 
no longer accessible. This happens during the bonnie++ "create many 
small files in random order" benchmark.

The "does this ever happen?" messages happen earlier.

I am attaching some debug info I gathered. I also have "debugfs.reiser4 
-t" output, but it's too large to send to this list I guess (3MB).

Answers please cc'd to my email address.

Best regards
Martin

-- 
Martin Wilck                Phone: +49 5251 8 15113
Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
Heinz-Nixdorf-Ring 1        mailto:Martin.Wilck@Fujitsu-Siemens.com
D-33106 Paderborn           http://www.fujitsu-siemens.com/primergy


[-- Attachment #2: debug.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 18773 bytes --]

                 reply	other threads:[~2004-09-08 15:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=413F259A.5010501@fujitsu-siemens.com \
    --to=martin.wilck@fujitsu-siemens.com \
    --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.