From: "Pedro M. Rodrigues" <pmanuel@myrealbox.com>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@suse.de>, tigran@veritas.com
Subject: Re: [reiserfs] SPEC SFS fails at low loads...
Date: Thu, 8 Feb 2001 11:47:34 +0100 [thread overview]
Message-ID: <3A828756.9682.4BCA4046@localhost> (raw)
In-Reply-To: Tigran Aivazian's message of "7 Feb 2001 17:37:30 +0100"
In-Reply-To: <ouphf26m6ez.fsf@pigdrop.muc.suse.de>
Btw, GFS (http://www.sistina.com) also needs 64bit inode
number support. They offer a patch called inode.patch that is a
backport of the 2.4 code.
Pedro
On 8 Feb 2001, at 0:15, Andi Kleen wrote:
> 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/
>
-
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-08 10:43 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
2001-02-08 10:47 ` Pedro M. Rodrigues [this message]
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=3A828756.9682.4BCA4046@localhost \
--to=pmanuel@myrealbox.com \
--cc=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