NSLU2-Linux
view · edit · print · history

Optware.Nfs-utils History

Hide minor edits - Show changes to markup

August 31, 2011, at 08:53 PM by noisybit -- Fixed table
Deleted line 104:
June 11, 2007, at 03:37 PM by Phil Endecott -- Warn that setting anonuid=0 is a serious security hole
Added lines 60-61:

(What you're doing there, by adding "all_squash,anonuid=0", is making the NFS server treat all accesses as if they were done by root. That is a very major security issue. I imagine that the OpenOffice? read-only problem is caused because of some sort of locking problem; you should find and fix that.)

June 06, 2007, at 12:23 PM by bloo --
Changed line 105 from:
blooLinksys NSLU2, 802.11g network, mount options: rw,rsize=8192,wsize=8192,tcp200718681646150117180918751924181541
to:
blooBuffalo WHR-G54S? OpenWrt, 802.11g network, mount options: rw,rsize=8192,wsize=8192,tcp200718681646150117180918751924181541
June 06, 2007, at 12:21 PM by bloo -- adding benchmarks
Added line 105:
blooLinksys NSLU2, 802.11g network, mount options: rw,rsize=8192,wsize=8192,tcp200718681646150117180918751924181541
March 21, 2007, at 11:22 AM by Phil Endecott -- Suggest the Linux NFS FAQ and HOWTO for performance hints
Changed lines 19-28 from:

(edit by TomTalpey? to strike through the client sync option. This option single-threads all NFS writes and completely kills write performance. See shettj's result in the table below, for example. It is useful only if the server is misbehaving badly.)

to:

The 'sync' option

See the Linux NFS FAQ and the "Performance" section of the Linux NFS HOWTO for much detail about synchronous vs. asycnhronous mode the effect on performance. A brief summary is as follows:

  • If you give the 'sync' option in the mount command, or in /etc/fstab/, the client will wait for the server to confirm that the data has been written to the disk after every write operation. This is safe against conditions such as the disk becoming full, encountering a bad sector, the power failing, or you rebooting the server, and is ideal for valuable data such as files that you are editing. But it can be slow.
  • If you give the 'async' option writes may be delayed, and there is no guarantee that the data is actually on the disk until the application closes the file or terminates. This is fine for low-value data where speed is important, e.g. your MythTV? backend.

If you are tempted to use async mode for valuable data, do investigate the other parameters (and in particular try increasing the write block size, wsize) first.

March 14, 2007, at 02:52 PM by Tom Talpey -- Add new (really high) performance result. Strike through the (really bad) \\\"sync\\\" option recommendations.
Changed lines 16-17 from:

By JamesCC?: If you are a nfs novice, you might want to have a read of the unfs3 package (just for setting up exports file and clients). When mounting on the client (a Gentoo linux PC), I found when using default nfs options it seemed to take 5+ minutes to mount. I found the following settings gave practically immediate mounting (I've included options on by default for clarity)... mount -o vers=3,tcp,sync,nolock,intr,hard,rw <nslu2_ip>:<dir_in_exports> <client_mount_point> ... Maybe it is the use of tcp? Or is it the use of version 3? Who knows but it works for me!

to:

By JamesCC?: If you are a nfs novice, you might want to have a read of the unfs3 package (just for setting up exports file and clients). When mounting on the client (a Gentoo linux PC), I found when using default nfs options it seemed to take 5+ minutes to mount. I found the following settings gave practically immediate mounting (I've included options on by default for clarity)... mount -o vers=3,tcp,sync,nolock,intr,hard,rw <nslu2_ip>:<dir_in_exports> <client_mount_point> ... Maybe it is the use of tcp? Or is it the use of version 3? Who knows but it works for me!

Added lines 19-22:

(edit by TomTalpey? to strike through the client sync option. This option single-threads all NFS writes and completely kills write performance. See shettj's result in the table below, for example. It is useful only if the server is misbehaving badly.)



Changed lines 49-50 from:
 mount -t nfs -o vers=3,tcp,sync,lock,intr,hard,rw <NSLU2 ip>:/share/flash/data/<share name> <mountpoint>
to:
 mount -t nfs -o vers=3,tcp,sync,lock,intr,hard,rw <NSLU2 ip>:/share/flash/data/<share name> <mountpoint>
Changed lines 108-109 from:
to:
Tom TalpeySlug with large i/o's enabled (details to follow), deunderclocked, ext2 filesystem, Netgear GS105? switch, 100MBit network, mount options: rw,tcp,rsize=131072,wsize=13107264006095562652242438258812678766023243
February 13, 2007, at 01:05 PM by carrick --
Changed lines 89-90 from:
Namecommentswrite KB/sread KB/s
to:
Namecommentswrite KB/sread KB/s
February 13, 2007, at 01:04 PM by carrick --
Changed lines 89-90 from:
Namecommentswrite KB/sread KB/s
to:
Namecommentswrite KB/sread KB/s
February 13, 2007, at 01:01 PM by carrick --
Changed lines 89-90 from:
Namecommentswrite KB/sread KB/s
to:
Namecommentswrite KB/sread KB/s
February 13, 2007, at 01:00 PM by carrick --
Changed lines 101-102 from:
Carrick MGiga bit switch nfsvers=3,user,suid,dev,rsize=8192,wsize=8192,noatime,exec3792339033032876585171533348303737243
Carrick MGigabit Switch vers=3,tcp,nolock,intr,rsize=16384,wsize=16384,exec,rw4231382037643261565278522448304129165
to:
Carrick MBelkin 5-Port Gigabit Switch F5D5141?-5 nfsvers=3,user,suid,dev,rsize=8192,wsize=8192,noatime,exec3792339033032876585171533348303737243
Carrick MBelkin 5-Port Gigabit Switch F5D5141?-5 vers=3,tcp,nolock,intr,rsize=16384,wsize=16384,exec,rw4231382037643261565278522448304129165
February 07, 2007, at 11:30 PM by Jan Girlich -- added Jan Girlich
Changed lines 103-104 from:
to:
Jan GirlichSiemens Gigaset se105, 100MBit network, deunderclocked slug, nfs4 mount options: auto,rw,nodev,rsize=32768,wsize=32768,proto=tcp,retry=10,hard,intr419641293968373788522451715019400078
February 01, 2007, at 10:33 PM by carrick --
Changed lines 102-105 from:
Carrick MGigabit Switch vers=3,tcp,nolock,intr,rsize=16384,wsize=16384,exec,rw 0 0
 || 4231 || 3820 || 3764 || 3261 || 56 || 5278 || 5224 || 4830 || 4129 || 165 ||
to:
Carrick MGigabit Switch vers=3,tcp,nolock,intr,rsize=16384,wsize=16384,exec,rw4231382037643261565278522448304129165
February 01, 2007, at 10:31 PM by carrick --
Changed lines 102-105 from:
to:
Carrick MGigabit Switch vers=3,tcp,nolock,intr,rsize=16384,wsize=16384,exec,rw 0 0
 || 4231 || 3820 || 3764 || 3261 || 56 || 5278 || 5224 || 4830 || 4129 || 165 ||
February 01, 2007, at 09:35 PM by carrick --
Changed lines 101-102 from:
Carrick Mnfsvers=3,user,suid,dev,rsize=8192,wsize=8192,noatime,exec3792339033032876585171533348303737243
to:
Carrick MGiga bit switch nfsvers=3,user,suid,dev,rsize=8192,wsize=8192,noatime,exec3792339033032876585171533348303737243
February 01, 2007, at 09:32 PM by carrick --
Changed lines 101-102 from:
to:
Carrick Mnfsvers=3,user,suid,dev,rsize=8192,wsize=8192,noatime,exec3792339033032876585171533348303737243
December 03, 2006, at 07:52 AM by Rene Dohmen --
Changed line 37 from:
 /share/hdd/data   192.168.0.0/255.255.0.0(rw,sync,no_root_squash)
to:
 /share/hdd/data   192.168.0.0/255.255.0.0(rw,sync,all_squash,anonuid=0)
December 03, 2006, at 07:51 AM by Rene Dohmen --
Changed lines 26-29 from:

Problem : when using OpenOffice.org from a Linux client with a default NFS setup as described above, by default documents will be opened as readonly.

Solution : By editing /opt/etc/exports documents can be updated with OpenOffice.org.

to:

Problem : when using OpenOffice.org from a Linux client with a default NFS setup as described above, by default documents will be opened as readonly.

Solution : By editing /opt/etc/exports, documents can be updated with OpenOffice.org.

December 03, 2006, at 07:48 AM by Rene Dohmen --
Changed lines 26-29 from:

Problem : when using [http://www.openoffice.org/index.html OpenOffice?.org] from a Linux client with a default NFS setup as described above, by default documents will be opened as readonly.

Solution : By editing /opt/etc/exports documents can be updated with [http://www.openoffice.org/index.html OpenOffice?.org].

to:

Problem : when using OpenOffice.org from a Linux client with a default NFS setup as described above, by default documents will be opened as readonly.

Solution : By editing /opt/etc/exports documents can be updated with OpenOffice.org.

Changed lines 42-43 from:

Editing with [http://www.openoffice.org/index.html OpenOffice?.org] works fine now !

to:

Editing with OpenOffice.org works fine now !

December 03, 2006, at 07:41 AM by Rene Dohmen -- OpenOffice section added
Added lines 24-48:

NFS and OpenOffice?

Problem : when using [http://www.openoffice.org/index.html OpenOffice?.org] from a Linux client with a default NFS setup as described above, by default documents will be opened as readonly.

Solution : By editing /opt/etc/exports documents can be updated with [http://www.openoffice.org/index.html OpenOffice?.org].

Default /opt/etc/exports :

 /share/hdd/data   192.168.0.0/255.255.0.0(rw,sync,no_root_squash)
 /share/hdd/conf   192.168.0.0/255.255.0.0(ro,sync,no_root_squash)
 /share/flash/data 192.168.0.0/255.255.0.0(rw,sync,no_root_squash)
 /share/flash/conf 192.168.0.0/255.255.0.0(ro,sync,no_root_squash)

After editing :

 /share/hdd/data   192.168.0.0/255.255.0.0(rw,sync,no_root_squash)
 /share/hdd/conf   192.168.0.0/255.255.0.0(ro,sync,no_root_squash)
 /share/flash/data 192.168.0.0/255.255.0.0(rw,sync,all_squash,anonuid=0)
 /share/flash/conf 192.168.0.0/255.255.0.0(ro,sync,no_root_squash)

Editing with [http://www.openoffice.org/index.html OpenOffice?.org] works fine now !

The NSLU2 is mounted by :

 mount -t nfs -o vers=3,tcp,sync,lock,intr,hard,rw <NSLU2 ip>:/share/flash/data/<share name> <mountpoint>

July 25, 2006, at 08:12 PM by JohnS -- add results
Changed lines 72-76 from:
mhomscheidtLinksys WRT54GL? Router, 100MBit network, mount options: Mac OS X default values312131412860210630433843384413416271
to:
mhomscheidtLinksys WRT54GL? Router, 100MBit network, mount options: Mac OS X default values312131412860210630433843384413416271
schettjturboslug unmanaged switch 100MBit network, mount options: vers=3,tcp,sync,nolock,intr,hard,rw396397396394505565595358184196204
schettjsame... mount options: vers=3,tcp,nolock,intr,rsize=8192,wsize=8192,rw3683376436573011775446533353334923134
schettjsame... mount options: vers=3,tcp,nolock,intr,rsize=16384,wsize=16384,rw4196430241293261775626568855055120138
May 20, 2006, at 05:42 PM by mhomscheidt -- Addition of own benchmark results
Changed lines 71-72 from:
crs_mchlnetgearFS605 switch, 100MBit network, mount options:vers=3,tcp,nolock,intr,rsize=8192,wsize=81922560242622061753243683387838203737182
to:
crs_mchlnetgearFS605 switch, 100MBit network, mount options:vers=3,tcp,nolock,intr,rsize=8192,wsize=81922560242622061753243683387838203737182
mhomscheidtLinksys WRT54GL? Router, 100MBit network, mount options: Mac OS X default values312131412860210630433843384413416271
December 18, 2005, at 11:25 AM by crs_mchl --
Added line 71:
crs_mchlnetgearFS605 switch, 100MBit network, mount options:vers=3,tcp,nolock,intr,rsize=8192,wsize=81922560242622061753243683387838203737182
December 11, 2005, at 01:47 AM by JamesCC -- typos
Changed lines 16-17 from:

By JamesCC?: If you are a nfs novice, you might want to have a read of unfs3 package (just for setting up exports file and clients). When mounting on the clients, I found using default nfs options seemed to make it take 5+ minutes to mount. I following settings gave practically immediate mounting (I've include options on by default for clarity)... mount -o vers=3,tcp,sync,nolock,intr,hard,rw <nslu2_ip>:<dir_in_exports> <client_mount_point> ... Maybe it is the use of tcp? Or is it the use of version 3? Who knows but it works for me!

to:

By JamesCC?: If you are a nfs novice, you might want to have a read of the unfs3 package (just for setting up exports file and clients). When mounting on the client (a Gentoo linux PC), I found when using default nfs options it seemed to take 5+ minutes to mount. I found the following settings gave practically immediate mounting (I've included options on by default for clarity)... mount -o vers=3,tcp,sync,nolock,intr,hard,rw <nslu2_ip>:<dir_in_exports> <client_mount_point> ... Maybe it is the use of tcp? Or is it the use of version 3? Who knows but it works for me!

December 11, 2005, at 01:43 AM by JamesCC -- Suggested options for mounting - the default options where taking me 5+ minutes to mount
Added lines 16-17:

By JamesCC?: If you are a nfs novice, you might want to have a read of unfs3 package (just for setting up exports file and clients). When mounting on the clients, I found using default nfs options seemed to make it take 5+ minutes to mount. I following settings gave practically immediate mounting (I've include options on by default for clarity)... mount -o vers=3,tcp,sync,nolock,intr,hard,rw <nslu2_ip>:<dir_in_exports> <client_mount_point> ... Maybe it is the use of tcp? Or is it the use of version 3? Who knows but it works for me!

June 18, 2005, at 02:33 AM by tman --
Changed line 51 from:
NameSizeNumber of filesFile Size
to:
NameSizeNumber of filesFile Size
Changed lines 58-60 from:

Warning: the script will not delete any files it created - anyway use it at your own risk!

to:

Warning: the script will not delete any files it created - use it at your own risk!

Changed lines 62-64 from:
Namecommentswrite KB/sread KB/s
  hugebigmedsmalltinyhugebigmedsmalltiny
to:
Namecommentswrite KB/sread KB/s
  hugebigmedsmalltinyhugebigmedsmalltiny
Changed line 66 from:
Geert JanssenNetGear? MR814v2? Router, 100MBit network, mount options: rsize=8192,wsize=8192302931213065289224517151205019449136
to:
Geert JanssenNetGear MR814v2 Router, 100MBit network, mount options: rsize=8192,wsize=8192302931213065289224517151205019449136
June 17, 2005, at 06:07 PM by mongolito404 -- mongolito404\
Changed lines 67-69 from:
Geert JanssenNetGear? MR814v2? Router, 100MBit network, mount options: rsize=8192,wsize=8192302931213065289224517151205019449136
to:
Geert JanssenNetGear? MR814v2? Router, 100MBit network, mount options: rsize=8192,wsize=8192302931213065289224517151205019449136
mongolito404Lowcost switch, 100MBit network, mount options: vers=3,tcp,nolock,intr,rsize=8192,wsize=81922994286027082585404530453044524376160
mongolito404Lowcost switch, 100MBit network, mount options: vers=3,udp,nolock,intr,rsize=8192,wsize=81923220282830842959605446544652785224170
January 07, 2005, at 02:21 AM by Geert Janssen --
Added line 67:
Geert JanssenNetGear? MR814v2? Router, 100MBit network, mount options: rsize=8192,wsize=8192302931213065289224517151205019449136
January 04, 2005, at 11:31 AM by madrat91 --
Changed line 55 from:
smallfiles10 MB500500 MB
to:
smallfiles1 MB500500 MB
January 04, 2005, at 10:46 AM by madrat91 --
Added lines 22-24:

Speed measurement

manual

Added lines 35-38:
Added lines 41-66:

Automatic benchmark:

In the yahoo group's file section you will find a NFS benchmark script (files->other files->nfs_benchmark.tar.bz). The script creates several portfolios on your local harddisk and transfers from your maschine to the slug and back. The throughput is measured and a line for the following table is generated. The script needs about 2.2 GB free space on your local harddisk and on your slug. It only takes about 20 minutes.

So please download the script, customize it and post your results here!

Portfolio overview:

NameSizeNumber of filesFile Size
hugefiles500 MB1500 MB
bigfiles100 MB5500 MB
mediumfiles10 MB50500 MB
smallfiles10 MB500500 MB
tinyfiles1 KB51205 MB

Warning: the script will not delete any files it created - anyway use it at your own risk!

Benchmark results:

Namecommentswrite KB/sread KB/s
  hugebigmedsmalltinyhugebigmedsmalltiny
madrat91Zonet Switched Hub, 100MBit network, mount options: rsize=8192,wsize=81922098229522061875414970517148764571160
January 03, 2005, at 04:46 AM by wsgaskins --
Changed lines 19-33 from:
 dyoung-HNY: http://de.groups.yahoo.com/group/nslu2-german/message/47
to:
 dyoung-HNY: http://de.groups.yahoo.com/group/nslu2-german/message/47

After some primitive benchmarking of the kernel-mode NFS using copying of the Unslung-able v3.17 build sub-directories residing on a Western Digital 160GB USB 2.0 hard drive over to a local hard drive on a Linux 2.4.24 Debian machine. Transfers are made over a 100MB ethernet full-duplex network through a D-LINK DI-614+ gateway switch and timed using the bash 'time' command.

(I have /home/slug nfs mounted to /share/hdd/data/slug)

Results:

 /home/slug/build/tmp/deploy  -- 110972kB,   890 files ==> (110972 kB / 26.5 sec) = 4187 kB/s read
 /home/slug/build/tmp/staging -- 130896kB, 10515 files ==> (130986 kB / 73.8 sec) = 1773 kB/s read 
 /home/slug/build/tmp/cross   -- 109992kB,  2879 files ==> (109992 kB / 36.2 sec) = 3038 kB/s read

 single 51MB mpg file  -- write to NSLU via nfs:  ==> (52600kB / 25.4 sec)   = 2070kB/s write
 single 255MB mpg file -- read from NSLU via nfs: ==> (261508 kB / 49.1 sec) = 5326 kB/s read
January 03, 2005, at 03:53 AM by wsgaskins --
Changed lines 1-19 from:

Please add content here.

to:

The package nfs-utils is the package of utilities and configuration files to enable the kernel-mode NFS that is compiled into Unslung-able v3.16 and later.

Be sure that you have the portmap ipkg installed.

Then to use kernel-mode NFS, you first need to:

 ipkg remove nfs-server

if you have been using NFS previously and it is installed. Then you can:

 ipkg install nfs-utils

That's it.

The example exports file is located in /opt/doc/nfs-utils/exports

Copy this file over to /opt/etc/exports and edit it as you wish.


And, according to dyoung:

 dyoung-HNY: kernel nfs is around twice as fast as unfs3; according to some benchmarks our german friends did.
 dyoung-HNY: http://de.groups.yahoo.com/group/nslu2-german/message/47
December 29, 2004, at 11:06 PM by ka6sox --
Changed line 1 from:

Describe {{Nfs-utils}} here.

to:

Please add content here.

Page last modified on August 31, 2011, at 08:53 PM