From: Andi Kleen <ak@suse.de>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [reiserfs] SPEC SFS fails at low loads...
Date: 08 Feb 2001 00:15:16 +0100 [thread overview]
Message-ID: <ouphf26m6ez.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0102071633331.712-100000@penguin.homenet>
In-Reply-To: Tigran Aivazian's message of "7 Feb 2001 17:37:30 +0100"
Tigran Aivazian <tigran@veritas.com> writes:
> Hi,
>
> Under 2.4.1, after a little bit of running SPEC SFS (with NFSv3) I get
> these messages on the server:
>
> vs-13042: reiserfs_read_inode2: [0 1 0x0 SD] not found
> vs-13048: reiserfs_iget: bad_inode. Stat data of (0 1) not found
> vs-13048: reiserfs_iget: bad_inode. Stat data of (0 1) not found
> vs-13048: reiserfs_iget: bad_inode. Stat data of (0 1) not found
>
> and the run aborts.
>
> Any clues?
Reiserfs really needs 64bit of inode in the NFS file handles, otherwise
this happens as soon as you run out of the file handle cache with many
active clients. The 2.2 code did a brute force search in this case (the
handles are unique in 32bit, it's just very costly to look them up without
the other 32bit), but it usually consumed so much CPU time that people
thought the server crashed.
There are patches to do that for knfsd for both 2.2 and 2.4, but they
haven't been merged yet. It needs a small VFS enhancement and knfsd changes.
Note that stock (unpatched) unfsd also doesn't work in all cases for other
reasons, it makes assumptions about the inode space that do not work out
on a longer used reiserfs. This has also been fixed.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-07 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 16:35 [reiserfs] SPEC SFS fails at low loads Tigran Aivazian
2001-02-07 23:15 ` Andi Kleen [this message]
2001-02-08 10:47 ` Pedro M. Rodrigues
2001-02-08 0:02 ` Chris Mason
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=ouphf26m6ez.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox