Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

I/O Errors when Uploading large files via NFS, UnRAID 6.8.3

Featured Replies

I searched for the answer for a couple of hours without success... So I figured I would ask here!

Recently, I had to do a fresh install of Pop!OS on my main rig because I managed to destroy it!

Since then, when trying to transfer large file to my Unraid server through NFS, I always get I/O errors and file corruption.

I have a feeling it has to do with caching but I am not certain... can someone point me in the right direction?

here is an example of how my shares are mounted in fstab:

[unraid server ip]:/mnt/user/[mount point]  /home/normand/NFS/NORMAND-NAS-01/[mount point] nfs defaults,timeo=14,soft 0 0

 

I remember having similar issues in the past but can't remember what I did to fix it.

 

 

Have a nice day all!

Edited by Normand_Nadon

  • Normand_Nadon changed the title to I/O Errors when Uploading large files via NFS, UnRAID 6.8.3
  • 3 weeks later...
  • Author

Sorry for bumping my own thread again... but this has become a nightmare!
I can't send medium to large files to my server because they always give me I/O errors. I am mostly certain it has something to do with caching, but I can't figure-out how to solve it...

Do you try other NFS mounting method ? I always transfer file through NFS without problem.

Edited by Vr2Io

  • Author
26 minutes ago, Vr2Io said:

Do you try other NFS mounting method ? I always transfer file through NFS without problem.

 

Yeah, me too! I have been using NFS for years... And using it in Unraid for some time too.

I had a new error I have never seen before just now... 
Maybe it will give off a clue... It said "Splicing error" and again, the I/O thing

 

I remember trying to mount my NFS shares with an older version of NFS before, but can't remember if it helped...

When I transfer files, I see that the client's buffer fills super fast before the transfer starts (like 2Gb in a few seconds)... that is why I suspect cache or buffer issue.

  • Author

There might be some issues here...

The block size seems huge... doesn't it?

 

I will try mounting with V2 instead of V3 and report
EDIT: V2 does not even work, server refuses...
image.thumb.png.e02c2695ae754a3772546872892d72a3.png
 

Edited by Normand_Nadon

I haven't verify what version NFS protocol I use, because I haven't problem. But I believe I use v2.

 

Pls have a try and update the result.

  • Author
1 minute ago, Vr2Io said:

I haven't verify what version NFS protocol I use, because I haven't problem. But I believe I use v2.

 

Pls have a try and update the result.

I tried, but I get this response:

 

mount.nfs: Protocol not supported

 

What OS in other end ? Can be change/config the protocol ver. in other end ?

Edited by Vr2Io

  • Author

I am running Pop!OS 20.10 (Ubuntu derivative)

 

When I force nfs V2 in /etc/fstab, I get the "protocol not supported" error

  • Author

Ok... I changed my mounting method from soft to:
hard,intr

 

I know this will get me other kinds of issues if the server goes down, but at least, I am able to upload files now!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.