Re: [gentoo-user] NFS Server Tuning
On 25 Jan 2008, at 22:40, Florian Philipp wrote: On Thu, 2008-01-24 at 19:19 -0600, Dan Farrell wrote: [...] and as the client (from `mount`): nfs:/mnt/storage on /home/media/storage type nfs(rw,rsize=65536,wsize=65536,soft,timeo=300,addr=192.168.1.88) /etc/fstab on the client looks like: nfs:/mnt/storage /home/media/storagenfs rsize=65536,wsize=65536,rw,async,soft,timeo=300 0 0 Of these options, rsize,wsize,and async are reputed to effect performance. ... [...] As far as I remember, rsize and wsize are negotiated between client and server. Those mount options just set an upper limit which is certainly not what you want. I'm even wondering that those settings are accepted at all! Normally, unsigned 16bit integer has a range from 0 to 65535. If you ask me, that's an off-by-one error just waiting to happen... This seems to suggest that 32768 is the largest figure that can be specified for rsize,wsize: http://www.mythtv.org/wiki/index.php/ Optimizing_Performance#NFS_servers Stroller. -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] NFS Server Tuning
On Sat, 2008-01-26 at 10:29 +, Stroller wrote: On 25 Jan 2008, at 22:40, Florian Philipp wrote: On Thu, 2008-01-24 at 19:19 -0600, Dan Farrell wrote: [...] and as the client (from `mount`): nfs:/mnt/storage on /home/media/storage type nfs(rw,rsize=65536,wsize=65536,soft,timeo=300,addr=192.168.1.88) /etc/fstab on the client looks like: nfs:/mnt/storage /home/media/storagenfs rsize=65536,wsize=65536,rw,async,soft,timeo=300 0 0 Of these options, rsize,wsize,and async are reputed to effect performance. ... [...] As far as I remember, rsize and wsize are negotiated between client and server. Those mount options just set an upper limit which is certainly not what you want. I'm even wondering that those settings are accepted at all! Normally, unsigned 16bit integer has a range from 0 to 65535. If you ask me, that's an off-by-one error just waiting to happen... This seems to suggest that 32768 is the largest figure that can be specified for rsize,wsize: http://www.mythtv.org/wiki/index.php/ Optimizing_Performance#NFS_servers Stroller. Ehmm, yes. NFS-docs approve this. From a programmer's perspective this number is still odd because it's one more than can fit into signed 16bit int and and 32767 less than unsigned 16bit int... maybe they had other reasons. Well, although neither info- nor man-pages mention it, I've found an old man-page [1] which states that these values default to 1024, therefore setting it to 32768 seems the best choice. [1] http://www.trinler.de/de/linux/man.html?command=nfs signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] NFS Server Tuning
On Thu, 2008-01-24 at 19:19 -0600, Dan Farrell wrote: [...] and as the client (from `mount`): nfs:/mnt/storage on /home/media/storage type nfs(rw,rsize=65536,wsize=65536,soft,timeo=300,addr=192.168.1.88) /etc/fstab on the client looks like: nfs:/mnt/storage /home/media/storagenfs rsize=65536,wsize=65536,rw,async,soft,timeo=300 0 0 Of these options, rsize,wsize,and async are reputed to effect performance. However, I do not see much of an effect between different rsize and wsize settings. I believe that over an uncongested 100T network it probably doesn't matter too much what rsize and wsize are. On a different share (same server) mounted async without [r|w]size set, performance (write, this time) was 11.2mb/s, roughly the same. Furthermore, I'm not sure these values are even valid. http://www.linuxdocs.org/HOWTOs/NFS-HOWTO/performance.html said that nfs3 goes only to 32768. [...] As far as I remember, rsize and wsize are negotiated between client and server. Those mount options just set an upper limit which is certainly not what you want. I'm even wondering that those settings are accepted at all! Normally, unsigned 16bit integer has a range from 0 to 65535. If you ask me, that's an off-by-one error just waiting to happen... signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] NFS Server Tuning
On 1/24/08, Stefan Onken [EMAIL PROTECTED] wrote: Any ideas how to improve the speed ? noatime? -- Arttu V. -- gentoo-user@lists.gentoo.org mailing list
RE: [gentoo-user] NFS Server Tuning
Man fstab man nfs{d} man mount and search for sync write options. Wsize
and rsize=8192 and wsize=8192 might work but I think they are deprecated.
Althought, async or sync might still be used. Use these options when mouting
your nfs share or make them permanent in your fstab file. Gentoo-wiki has a
good guide on this. I would have given you a good set of options but I'm not
able to access the inet.
-Original Message-
From: Stefan Onken [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 24, 2008 2:18 PM
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] NFS Server Tuning
Hello,
I am running a x86 gentoo box as a nfs server. As a filesystem I am
using XFS on a 3ware Raid system.
The 3ware systems seems to be quite quick, although access via NFS
seems to be very slow. Any ideas how I can improve speed ? I was
expected a speed only limited by the 100 Mbit network. Now, the
speed is so slow, that reading/writing at the same time is nearly
impossible.
Any ideas how to improve the speed ?
hdparm on the gentoo box machine:
backup3 ~ # hdparm -tT /dev/sdb
/dev/sdb:
Timing cached reads: 4108 MB in 2.00 seconds = 2054.34 MB/sec
Timing buffered disk reads: 232 MB in 3.01 seconds = 77.09 MB/sec
/etc/exports on the gentoo box:
/mnt/backup/ 192.168.1.0/24
(rw,no_root_squash,async,no_subtree_check)
I am not even able to run a bonnie benchmark on the client. It seems
to hang while doing rewriting. Running bonnie on the nfs server
gives a fast result.
/etc/fstab on the client:
192.168.1.3:/mnt/backup /mnt/backup nfs
rw,users,async 0
http://pastebin.com/m72ae9d47
Any ideas ?
--
www.stonki.de:the more I see, the more I know...
www.proftpd.de: Deutsche ProFTPD Dokumentation
www.krename.net: Der Batch Renamer für KDE
www.kbarcode.net: Die Barcode Solution für KDE
--
gentoo-user@lists.gentoo.org mailing list
--
gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] NFS Server Tuning
On Thu, 24 Jan 2008 22:58:54 +0200 Arttu V. [EMAIL PROTECTED] wrote: On 1/24/08, Stefan Onken [EMAIL PROTECTED] wrote: Any ideas how to improve the speed ? noatime? I wouldn't expect that to help too much. Async is the #1 speed improvement on my network; I get disc access speeds of 11.5 mb/s on mine, which effectively maxes out the network.In /etc/exports on the server I have: /mnt/storage 192.168.0.0/16(rw,async,no_subtree_check,no_root_squash) and as the client (from `mount`): nfs:/mnt/storage on /home/media/storage type nfs(rw,rsize=65536,wsize=65536,soft,timeo=300,addr=192.168.1.88) /etc/fstab on the client looks like: nfs:/mnt/storage /home/media/storagenfs rsize=65536,wsize=65536,rw,async,soft,timeo=300 0 0 Of these options, rsize,wsize,and async are reputed to effect performance. However, I do not see much of an effect between different rsize and wsize settings. I believe that over an uncongested 100T network it probably doesn't matter too much what rsize and wsize are. On a different share (same server) mounted async without [r|w]size set, performance (write, this time) was 11.2mb/s, roughly the same. Furthermore, I'm not sure these values are even valid. http://www.linuxdocs.org/HOWTOs/NFS-HOWTO/performance.html said that nfs3 goes only to 32768. wdelay and no_wdelay might have an effect, depending on your application. I no longer tweak those values. There are some network performance tweaks as well; their effect wasn't particularly noticable to me, but look http://www.linuxdocs.org/HOWTOs/NFS-HOWTO/performance.html for more information on 5.4. Memory Limits on the Input Queue, 5.3. Number of Instances of NFSD, and 5.5. Overflow of Fragmented Packets were interesting to me. Finally, NFS4 is reputed to be much faster in certain cases. Hope that helps. I would be very interested in your findings. Be well, Dan Farrell -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] nfs server problem
On Wed, 03 Oct 2007 08:54:30 -0230 Roger Mason [EMAIL PROTECTED] wrote: Hello, I installed a vanilla 2.6.20 kernel in order to (eventually) run kerrighed. The kernel boots fine but the nfs server won't start and I see this in the logs: Oct 3 07:34:40 lowalbite rpc.statd[103835]: Version 1.1.0 Starting Oct 3 07:34:41 lowalbite nfsd: last server has exited Oct 3 07:34:41 lowalbite nfsd: unexporting all filesystems Oct 3 07:34:41 lowalbite nfsd[103901]: nfssvc: Address already in use When I boot into gentoo 2.6.22 this problem goes away, so I assume there is some difference in kernel configuration. I have not been able to find what that is by comparing the NFS_* entries in the respective .congig files: they are identical. Can someone suggest how I might track this down? Thanks, Roger It seems like there's two options: either you're trying to run 2 nfs servers, or you're trying to run nfs threads that for some reason conflict with each other. anyway, the solution I suggest is checking the output of 'netstat -l -p -n' to see whether anything really is listening on those ports. If not, try using a quick script to keep reading the output of the previous netstat command and checking consistantly to see whether anything's listening on those ports while you restart nfs. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] nfs server problem
Hi Dan, Dan Farrell [EMAIL PROTECTED] writes: On Wed, 03 Oct 2007 08:54:30 -0230 Roger Mason [EMAIL PROTECTED] wrote: Hello, I installed a vanilla 2.6.20 kernel in order to (eventually) run kerrighed. The kernel boots fine but the nfs server won't start and I see this in the logs: Oct 3 07:34:40 lowalbite rpc.statd[103835]: Version 1.1.0 Starting Oct 3 07:34:41 lowalbite nfsd: last server has exited Oct 3 07:34:41 lowalbite nfsd: unexporting all filesystems Oct 3 07:34:41 lowalbite nfsd[103901]: nfssvc: Address already in use It seems like there's two options: either you're trying to run 2 nfs servers, or you're trying to run nfs threads that for some reason conflict with each other. anyway, the solution I suggest is checking the output of 'netstat -l -p -n' to see whether anything really is listening on those ports. If not, try using a quick script to keep reading the output of the previous netstat command and checking consistantly to see whether anything's listening on those ports while you restart nfs. -- That is agood idea -- I'll try it tomorrow. In the meantime I am working round it by setting the port(s) in /etc/conf.d/nfs, but it would certainly be cleaner to find and eliminated the conflict. Thanks for your help. Roger -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] nfs server problem
The error you are receiving indicates that you already have a service occupying the port that the nfs server wants to bind to, however only one service can bind to a port at any one given time. So you must find the service that is occupying the port nfs server wants to bind to and either disable that service or configure it to run on another port.
Re: [gentoo-user] NFS Server
Oscar Carlsson wrote: Make sure portmap is installed... :) On 10/9/05, Bruno Gola [EMAIL PROTECTED] wrote: Hi there everyody, Im trying to run a nfs server here, but im having some problems. My kernel is compiled to work with NFS as server or client and ive already emerge nfs-utils. Ok, but when i was starting the server, look what appears: (the /etc/exports is OK) br slackware # /etc/init.d/nfs status * status: stopped br slackware # /etc/init.d/nfs start * Starting idmapd ... [ ok ] * Starting NFS statd ... [ ok ] * Exporting NFS directories ... [ ok ] * Starting NFS daemon ... * Error starting NFS daemon [ !! ] * Starting NFS mountd ... Cannot register service: RPC: Timed out * Error starting NFS mountd [ !! ] br slackware # Well, slackware is only the directory that i was when i've tried to start the nfs :-) the dist. is Gentoo Does anyone knows what is happening ? Thanks for any awnser, Bruno Gola -- gentoo-user@gentoo.org mailing list The problem was that my loopback network wasnt working before i've update... thanks for the comment! -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS Server
Make sure portmap is installed... :) On 10/9/05, Bruno Gola [EMAIL PROTECTED] wrote: Hi there everyody, Im trying to run a nfs server here, but im having some problems. My kernel is compiled to work with NFS as server or client and ive already emerge nfs-utils. Ok, but when i was starting the server, look what appears: (the /etc/exports is OK) br slackware # /etc/init.d/nfs status * status: stopped br slackware # /etc/init.d/nfs start * Starting idmapd ... [ ok ] * Starting NFS statd ... [ ok ] * Exporting NFS directories ... [ ok ] * Starting NFS daemon ... * Error starting NFS daemon [ !! ] * Starting NFS mountd ... Cannot register service: RPC: Timed out * Error starting NFS mountd [ !! ] br slackware # Well, slackware is only the directory that i was when i've tried to start the nfs :-) the dist. is Gentoo Does anyone knows what is happening ? Thanks for any awnser, Bruno Gola -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS Server
Bruno, Looks like portmap isnt started. Make sure portmap is started would be what I would do next. P Bruno Gola wrote: Hi there everyody, Im trying to run a nfs server here, but im having some problems. My kernel is compiled to work with NFS as server or client and ive already emerge nfs-utils. Ok, but when i was starting the server, look what appears: (the /etc/exports is OK) br slackware # /etc/init.d/nfs status * status: stopped br slackware # /etc/init.d/nfs start * Starting idmapd ...[ ok ] * Starting NFS statd ... [ ok ] * Exporting NFS directories ... [ ok ] * Starting NFS daemon ... * Error starting NFS daemon [ !! ] * Starting NFS mountd ... Cannot register service: RPC: Timed out * Error starting NFS mountd [ !! ] br slackware # Well, slackware is only the directory that i was when i've tried to start the nfs :-) the dist. is Gentoo Does anyone knows what is happening ? Thanks for any awnser, Bruno Gola -- gentoo-user@gentoo.org mailing list
