Re: 2.4 vs. 2.6 nfs client performance

[Jason Holmes <jholmes@psu.edu>]

Trond Myklebust wrote:
> 
> >>>>> " " == Jason Holmes <jholmes@psu.edu> writes:
> 
>      > Client nfs v3: null getattr setattr lookup access readlink 0 0%
>      > 744 0% 0 0% 129 0% 252 0% 0 0% read write create mkdir symlink
>      > mknod 873 0% 178574 14% 24 0% 0 0% 0 0% 0 0% remove rmdir
>      > rename link readdir readdirplus 24 0% 0 0% 0 0% 0 0% 18 0% 0 0%
>      > fsstat fsinfo pathconf commit 0 0% 3 0% 0 0% 1023451 84%
> 
>      > Client rpc stats: calls retrans authrefrsh 1204092 3 0
> 
> Something is seriously screwed up here: it should be impossible to get
> more commit requests than there are write requests.
> 
> Basically, commit is only sent if at least one unstable write has been
> sent, and is waiting on the commit list. The commit list itself is
> emptied before the RPC call gets sent. If the commit fails, it
> resends all pending writes.
> 
> IOW: it looks like you are seeing some form of list corruption. I
> suspect that the problem here might be something scribbling over the
> nfs_inode. Are you running with slab debugging, and stack overflow
> enabled?

I wasn't, but I'm recompiling test9-bk17 with all of the debugging
options turned on right now.  Is there anything in particular you want
me to do?

Thanks,

--
Jason Holmes


-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs