Linux NFS development
 help / color / mirror / Atom feed
From: Serge Sozonoff <serge@sozonoff.com>
To: NFS@lists.sourceforge.net
Cc: "Lever, Charles" <Charles.Lever@netapp.com>
Subject: Re: NFS and linux 2.6 series kernels
Date: Mon, 08 Mar 2004 16:18:05 +0100	[thread overview]
Message-ID: <404C8EAD.50705@sozonoff.com> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435DD0E@lavender-fe.eng.netapp.com>

Hi Charles,

 > can you report to the list your mount options and the output of nfsstat
 > -c
 > on your client (after such a transfer was attempted)?

Yes, I am using this as my mount options:
mount -o rsize=32768,wsize=32768,nfsvers=3,noatime nas:/Access.Share/system_images /mnt/images

I have also tried with a few different wsize and rsize like for example 8192 and I tried mounting with no options at all.
I am using UDP and cannot try TCP because my NAS server does not currently support it.

This is the output of nfsstat -c on the client after about 400Mb transfered at which point I canceled the transfer because otherwise it would take forever.
Interestingly the transfer starts at a screeming speed in comparison to a 2.4 kernel NFS client but then it all stops and kind
of bumps along. I am running on 100Mpbs ethernet, non switched but for the moment there is no other traffic on the lan.
My test basically consists of running partimage to back up my disk partitions to the nas.

Client rpc stats:
calls      retrans    authrefrsh
42095      211        0
Client nfs v2:
null       getattr    setattr    root       lookup     readlink
0       0% 0       0% 0       0% 0       0% 0       0% 0       0%
read       wrcache    write      create     remove     rename
0       0% 0       0% 0       0% 0       0% 0       0% 0       0%
link       symlink    mkdir      rmdir      readdir    fsstat
0       0% 0       0% 0       0% 0       0% 0       0% 0       0%

Client nfs v3:
null       getattr    setattr    lookup     access     readlink
0       0% 7       0% 0       0% 4       0% 8       0% 0       0%
read       write      create     mkdir      symlink    mknod
0       0% 41747  99% 2       0% 0       0% 0       0% 0       0%
remove     rmdir      rename     link       readdir    readdirplus
1       0% 0       0% 0       0% 0       0% 0       0% 0       0%
fsstat     fsinfo     pathconf   commit
317     0% 1       0% 0       0% 8       0%


Currently I am running 2.6.4-rc1-mm2 but I have also tried with kernel-2.6.3-gentoo-r2.

Thanks,
Serge




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

       reply	other threads:[~2004-03-08 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <482A3FA0050D21419C269D13989C61130435DD0E@lavender-fe.eng.netapp.com>
2004-03-08 15:18 ` Serge Sozonoff [this message]
2004-03-08 12:09 NFS and linux 2.6 series kernels Serge Sozonoff

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=404C8EAD.50705@sozonoff.com \
    --to=serge@sozonoff.com \
    --cc=Charles.Lever@netapp.com \
    --cc=NFS@lists.sourceforge.net \
    /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