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 <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
> 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 [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
