nfs good download speed but low upload speed.

rezad · 2024-02-18 00:14:46

I have nfs server on a client on my wifi lan.
I use it for file storage and mount that nfs export folder on my laptop so I can use it like a local folder.

when I download file from that folder to my laptop I have 30MB/s speed.
when I upload from my laptop to that folder speed is 3MB/s

I thought that the issue was maybe hdd of the lan client was fragmented or slow writing but when I try sshf mount I get the 30-40MB/s both ways.

this is the mount output:

mylan1:/mnt/data on /mnt/data type nfs4 (rw,nosuid,nodev,noexec,relatime,sync,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.101,local_lock=none,addr=192.168.1.102)

Last edited by rezad (2024-02-18 01:29:41)

seth · 2024-02-18 15:35:20

Does it speed up if you mount it "async"?

rezad · 2024-02-18 16:55:54

yes.

I now remembered that I had to add async to fstab because uploading files (when they are big enough that it takes time, freezes the kde dolphin file manager.
I had to add that async because when I uploaded a 8GB file it froze the file manager and after a while it just stuck with no upload.

is there any way to have both ? if I don't use async then upload of big files freezes my file manager. and if I do async I get 1/10 speed.

seth · 2024-02-18 20:13:24

Hold on, the mount output suggest that the nfs partition is mounted "sync", **not** "async"?

rezad · 2024-02-19 03:30:18

yes because I put that option in fstab for that mount.

as I said I had upload causing hangs of file mananger issues so I searched the internet and that was suggestied and I put it there and my upload hangs stopped. but my download speed became 1/10.

seth · 2024-02-19 09:28:51

So for clarification, the default "sync" mount gets you expectable throughput, only the (explicitly warned against) async mount exhibits the slow upload speed?
Rather try soft and lower the timeo (drastically) to deal w/ the dolphin freezes.

rezad · 2024-02-19 10:07:04

seth wrote:

So for clarification, the default "sync" mount gets you expectable throughput, only the (explicitly warned against) async mount exhibits the slow upload speed?
Rather try soft and lower the timeo (drastically) to deal w/ the dolphin freezes.

I had used nfs and recently have that upload freezing issue (which on big files(8GB) would hang the whole network and needs a reboot)

so I searched the internet and used that sync thing for making upload usable again.
but later (here) I found that speed becomes very low with that option.

the second part of your answer, I dont understand it.

d.ALT · 2024-02-19 15:10:02

rezad wrote:

the second part of your answer, I dont understand it.

NFS(5) wrote:

timeo=n
    The time in deciseconds (tenths of a second) the NFS client waits for a response before it retries an NFS request.

    For NFS over TCP the default timeo value is 600 (60 seconds). The NFS client performs linear backoff: After each retransmission the timeout is increased by timeo up to the maximum of 600 seconds.
    However, for NFS over UDP, the client uses an adaptive algorithm to estimate an appropriate timeout value for frequently used request types (such as READ and WRITE requests), but uses the timeo setting for infrequently used request types (such as FSINFO requests). If the timeo option is not specified, infrequently used request types are retried after 1.1 seconds. After each retransmission, the NFS client doubles the timeout for that request, up to a maximum timeout length of 60 seconds.

soft / softerr / hard
    Determines the recovery behavior of the NFS client after an NFS request times out. If no option is specified (or if the hard option is specified), NFS requests are retried indefinitely. If either the soft or softerr option is specified, then the NFS client fails an NFS request after retrans retransmissions have been sent, causing the NFS client to return either the error EIO (for the soft option) or ETIMEDOUT (for the softerr option) to the calling application.

    NB: A so-called "soft" timeout can cause silent data corruption in certain cases. As such, use the soft or softerr option only when client responsiveness is more important than data integrity. Using NFS over TCP or increasing the value of the retrans option may mitigate some of the risks of using the soft or softerr option.

[[ https://man.archlinux.org/man/nfs.5.en ]]

seth · 2024-02-19 15:13:07

If we ignore that for the moment, the last comment seems to contradict the previous one again and also "sync" is the default behavior.

Please configure the system so that it's fast, but freezes dolphin and post the output of "mount".
Then configure it so that it's slow but stable and post the output of "mount" for that condition.

rezad · 2024-02-20 02:39:50

no sync is no the default behavior.

when I use no option I get high upload speed but hangs with large files:
mount output

mylan1:/mnt/data on /mnt/data type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.101,local_lock=none,addr=192.168.1.102)

with sync used in fstab I get low upload speed but not hangs:
mount output

mylan1:/mnt/data on /mnt/data type nfs4 (rw,nosuid,nodev,noexec,relatime,sync,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.101,local_lock=none,addr=192.168.1.102)

"Then configure it so that it's slow but stable and post the output of "mount" for that condition." my first post has that.
and it is the second output here(with sync)

Last edited by rezad (2024-02-20 02:41:55)

seth · 2024-02-20 07:54:31

no sync is no the default behavior.

Sorry, I was mixig it up w/ the exportfs flag.

So basically the main problem is the freezing client behavior, I suspect b/c dolphin wants to stat the remote files or inspect their magic bytes or render image previews…, thrashes the FS and locks up because it waits for the remote file to be read.
=> add "soft,timeo=14" the mount options and see whether dolphin starts to behave.

rezad · 2024-02-20 15:10:25

seth wrote:

no sync is no the default behavior.
Sorry, I was mixig it up w/ the exportfs flag.
So basically the main problem is the freezing client behavior, I suspect b/c dolphin wants to stat the remote files or inspect their magic bytes or render image previews…, thrashes the FS and locks up because it waits for the remote file to be read.
=> add "soft,timeo=14" the mount options and see whether dolphin starts to behave.

with no sync option, right?

I tried and with 400MB file upload copy I see no difference with the buggy default (no sync option).

seth · 2024-02-20 15:18:44

So dolphin still freezes?
https://bugs.kde.org/show_bug.cgi?id=224438
https://bugs.kde.org/show_bug.cgi?id=317676
This looks bleak…

I'd suggest to hint "_netdev" but eg. https://www.opensuse-forum.de/thread/66 … erbar-ein/ (german, synology NAS) has that and a similar problem.
It also suggests that krusader isn't affected - can you confirm that?

d.ALT · 2024-02-20 15:49:15

"stupid" check: is this behaviour also happening when manual mounting by IP.ADD.RE.SS ?

Are you exporting single par-paths folders? Or are you following the export-root-first rule?

rezad · 2024-02-20 17:03:46

d.ALT wrote:

"stupid" check: is this behaviour also happening when manual mounting by IP.ADD.RE.SS ?
Are you exporting single par-paths folders? Or are you following the export-root-first rule?

my /etc/exports.d/data.exports
/mnt/data/ 192.168.1.0/24(rw,no_subtree_check)

for clarification, that /mnt/data is on the lan device, and I mount it on the same path on my laptop too.

and mounting via lan ip doesn't make a difference.

Last edited by rezad (2024-02-20 17:05:38)

rezad · 2024-02-20 17:11:38

seth wrote:

So dolphin still freezes?
https://bugs.kde.org/show_bug.cgi?id=224438
https://bugs.kde.org/show_bug.cgi?id=317676
This looks bleak…
I'd suggest to hint "_netdev" but eg. https://www.opensuse-forum.de/thread/66 … erbar-ein/ (german, synology NAS) has that and a similar problem.
It also suggests that krusader isn't affected - can you confirm that?

wow even kde4 had that?

I tried with krusader and copying from my laptop home to the locally mounted remote nfs still hangs the dolphin file manager and krusader.

seth · 2024-02-20 20:26:26

Is dolphin still active/accessing the NFS share while trying to use krusader?
And just to be sure: there's no problem when using eg. the midnight commander?

rezad · 2024-02-20 23:33:16

seth wrote:

Is dolphin still active/accessing the NFS share while trying to use krusader?
And just to be sure: there's no problem when using eg. the midnight commander?

when I use quit option in dolphin (I learned that dolphin still runs if you just close it) and then copy with krusader I still get the hang for krusader.

so I dont think the issue is dolphin perse.

seth · 2024-02-21 08:06:26

seth wrote:

there's no problem when using eg. the midnight commander?

Or just "cp"?

rezad · 2024-02-21 09:58:50

seth wrote:

seth wrote:
there's no problem when using eg. the midnight commander?
Or just "cp"?

I tried cp and rsync but I dont know how to see if the bug is there or not unless I open dolphinn while cp'ing and then dolphin is hanged.

d.ALT · 2024-02-21 10:04:50

<EDIT>
You could monitor $INTERFACE bandwidth / traffic, also.
(eg.: iftop)
</EDIT>

Well, just take note of "distance"/time

$ time cp -ar /ONE/HUGE/TEST/FOLDER /mnt/data/THE_HUGE_TEST_FOLDER/

Or:

$ rsync -hhhrvP --stats /ONE/HUGE/TEST/FOLDER /mnt/data/

Last edited by d.ALT (2024-02-21 10:12:08)

d.ALT · 2024-02-21 12:14:35

As for reference, here's my NFS mount options, in case you'd like to try 'em:

CLIENT - manual mount (script):

-tnfs -overs=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=NNN.NNN.NNN.NNN,local_lock=none,addr=NNN.NNN.NNN.NNN

SERVER - /etc/exports:

NNN.NNN.NNN.0/24(insecure,rw,async,no_subtree_check,no_auth_nlm,all_squash,anonuid=1000,anongid=1000)

seth · 2024-02-21 13:02:54

As long as the async copy runs through and doesn't freeze you're good (and mc has a TUI for you to follow)
For the KDE stuff, likely just use the nfs kio (nfs://)

rezad · 2024-02-22 04:01:48

seth wrote:

As long as the async copy runs through and doesn't freeze you're good (and mc has a TUI for you to follow)
For the KDE stuff, likely just use the nfs kio (nfs://)

sync copies is the one that works but is slow not async.

async (or default) it freezes the file manager.

if it was only file manager I would not have cared that much.
but when last week I tried to copy a huge file 8GB, and it froze the file manager and when I came back to my laptop not only file wasn't uploaded completely, the network was fronzen (hanged?) that made me restart my laptop.

I think I just use sync and tolerate the slow upload.

I first though it was my remote hdd slowing down and I needed the sync and other stuff because of it being hdd and maybe old or slow fragmneted one.
but with sshfs I dont have that issue.

seth · 2024-02-22 08:40:44

but when last week I tried to copy a huge file 8GB, and it froze the file manager and when I came back to my laptop not only file wasn't uploaded completely, the network was fronzen (hanged?) that made me restart my laptop.

* How exactly was the network "frozen"
* Can you replicate that and post the system journal of such boot?
* Do you get the same effect when uploading a huge file w/ cp (and no dolphin running, ideally from the multi-user.target)
*

seth wrote:

For the KDE stuff, likely just use the nfs kio (nfs://)

What might happen is that the remote side actually can't keep up and that you're jamming the wmem_max / tcp_wmem
https://www.cyberciti.biz/faq/linux-tcp-tuning/

Arch Linux

#1 2024-02-18 00:14:46

nfs good download speed but low upload speed.

#2 2024-02-18 15:35:20

Re: nfs good download speed but low upload speed.

#3 2024-02-18 16:55:54

Re: nfs good download speed but low upload speed.

#4 2024-02-18 20:13:24

Re: nfs good download speed but low upload speed.

#5 2024-02-19 03:30:18

Re: nfs good download speed but low upload speed.

#6 2024-02-19 09:28:51

Re: nfs good download speed but low upload speed.

#7 2024-02-19 10:07:04

Re: nfs good download speed but low upload speed.

#8 2024-02-19 15:10:02

Re: nfs good download speed but low upload speed.

#9 2024-02-19 15:13:07

Re: nfs good download speed but low upload speed.

#10 2024-02-20 02:39:50

Re: nfs good download speed but low upload speed.

#11 2024-02-20 07:54:31

Re: nfs good download speed but low upload speed.

#12 2024-02-20 15:10:25

Re: nfs good download speed but low upload speed.

#13 2024-02-20 15:18:44

Re: nfs good download speed but low upload speed.

#14 2024-02-20 15:49:15

Re: nfs good download speed but low upload speed.

#15 2024-02-20 17:03:46

Re: nfs good download speed but low upload speed.

#16 2024-02-20 17:11:38

Re: nfs good download speed but low upload speed.

#17 2024-02-20 20:26:26

Re: nfs good download speed but low upload speed.

#18 2024-02-20 23:33:16

Re: nfs good download speed but low upload speed.

#19 2024-02-21 08:06:26

Re: nfs good download speed but low upload speed.

#20 2024-02-21 09:58:50

Re: nfs good download speed but low upload speed.

#21 2024-02-21 10:04:50

Re: nfs good download speed but low upload speed.

#22 2024-02-21 12:14:35

Re: nfs good download speed but low upload speed.

#23 2024-02-21 13:02:54

Re: nfs good download speed but low upload speed.

#24 2024-02-22 04:01:48

Re: nfs good download speed but low upload speed.

#25 2024-02-22 08:40:44

Re: nfs good download speed but low upload speed.

Board footer