search

lixuewei / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

NFS server error when using another router (tomato FW) running transmission #1071

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Not sure, if NFS server error. Transmission running on another router works 
well if file size is small. Downloading 50MB+ will result in 
transmission-daemon program termination and partial write download on built-in 
NFS server on rt-n56u. Restarting transmission-daemon will not resume either.

2. I mount NFS client on tomato router using syntax "mount -t nfs -o nolock 
10.0.1.1:/media/AiDisk_a2/downloads /mnt/downloads". W/out -o nolock it will 
not mount. I tried installing nfs-utils optware, but no effect. 

What is the expected output? What do you see instead?
It should complete transmission download without error.

What version of the product are you using? On what operating system?

Please describe the problem as detailed as it's possible.
If you have connection problem, then syslog file is required. (please do
attach it as a file)
Note that if there will be a poor problem description the issue status will
be changed to 'Invalid'!

Original issue reported on code.google.com by leandro.ong@gmail.com on 16 Nov 2013 at 12:35

GoogleCodeExporter commented 9 years ago 
FW version:     3.4.3.7-072

Original comment by leandro.ong@gmail.com on 16 Nov 2013 at 12:40

GoogleCodeExporter commented 9 years ago 
Have to add information that NFS built-server is running well. I issue putty 
command on tomato router, "ls /mnt/downloads" and it gives me the NFS server 
contents.

Original comment by leandro.ong@gmail.com on 16 Nov 2013 at 12:45

GoogleCodeExporter commented 9 years ago 
    Solution, decrease rsize and wsize values. Now transmission working without errors...

    Current values:
    root@BTRouter2:/tmp/home/root# cat /proc/mounts
    ...
    10.0.1.1:/media/AiDisk_a2/downloads /tmp/mnt/downloads nfs rw,vers=3,rsize=65536,wsize=65536,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,addr=10.0.1. 0 0

    change mounting to:
    root@BTRouter2:/tmp/home/root# mount -t nfs -o nolock,rsize=32768,wsize=32768 10.0.1.1:/media/AiDisk_a2/downloads /mnt/downloads

Original comment by leandro.ong@gmail.com on 16 Nov 2013 at 4:12

GoogleCodeExporter commented 9 years ago 
Sorry, I got confused. I thought I'm downloading to NFS server. This is still 
problem even if I reduce buffer size to 4096.

Original comment by leandro.ong@gmail.com on 16 Nov 2013 at 5:57

GoogleCodeExporter commented 9 years ago 
Solved. Here is the correct mounting NFS client that works well with 
transmission-daemon, "mount -t nfs -o nolock,intr,hard,timeo=14,sync 
10.0.1.1:/media/AiDisk_a2/downloads /mnt/downloads"

Original comment by leandro.ong@gmail.com on 18 Nov 2013 at 7:04

GoogleCodeExporter commented 9 years ago 
Treat this issue as invalid.

Original comment by leandro.ong@gmail.com on 18 Nov 2013 at 7:05

GoogleCodeExporter commented 9 years ago 
Treat this issue as invalid.

Original comment by leandro.ong@gmail.com on 18 Nov 2013 at 7:05

GoogleCodeExporter commented 9 years ago

Original comment by Dr.Sydorenko.O on 18 Nov 2013 at 1:45