Beiträge von fop

On Windows 10, this is one of the ways to get to the Ethernet adapter Advanced properties .....

• Open Windows Settings
• Select Network and Internet
• click Change Adapter Options
• click on Local Area Connection for your adapter (in my case the Atheros L1 Gigabit)
• Click on Properties (bottom left) to open up the Local Area Connection Properties window
• Click on Configure, to open up the panel for the Ethernet adapter
• Finally click on the Advanced tab to see the panel as in the photo attached
• You can see the Task Offload highlighted in the photo. The default Value is On. I set mine to Off to avoid problems.

Problem now resolved but probably worth sharing.........

While transferring large files and folders of multiple files from Windows 10 across to the OMV folders the speed of transfers, initially beginning at around 60-80MB/s, slowly began to grind to a halt! It not only ground to a halt, I could only restart it again by resetting the Ethernet adapter in Windows. Smaller files transferred one at a time no issue (and big files up/downloading from the internet are no problem). The two machines are hard wire Ethernet connected both using gigabit adapters built in the Asus motherboards on each machine.

I began to suspect SMB/CIFS, the OMV system itself, incompatibility between Windows and OMV, you name it. I updated the Atheros Ethernet adapter drivers forwards and backwards - no difference. I checked/adjusted Atheros Advanced properties/settings for flow control, receive/transmit buffers etc - no difference. I googled until I got boggle-eyed. Big/fast transfers between drives within the Windows machine were fine, and OMV to Windows seemed OK, the problem was from Windows to OMV. I thought it might have been the Windows paging file too small to handle the big files I was transferring, so I set it from the standard 3GB to 10GB. Initially that seemed to do the trick and the transfer speeds seemed to hold at 50-80MB/s. Next day however the problem was back! And I was back to Google research!

Eventually I found one posting on a forum somewhere that pointed to it. In the Atheros adapter Advanced properties there's something called Task Offload which has a default value of ON. I hadn't messed with that as it didn't look relevant. I finally discovered that Task Offload, when ON, allows Windows to offload some comms transaction processing to the Atheros adapter. Unfortunately the Atheros L1 Gigabit adapter is not up to the job, and falls over under high loads! When that happens you have to reset the adapter (turn ethernet off then back on) to get it to work again. However - turn the Task Offload setting to the value OFF and it all works fine! Big/fast file transfers between machines are now handled without a problem. I've noticed the speed is slightly less (around 10-15%) that the initial maximum when Task Offload was ON, but that was no good when it gradually ground to a halt! So I'm very happy. Hope this helps others to avoid this problem with the Atheros, and maybe other adapters.

fop

First post for newbie OMV fan.........

I recently installed OMV on a now headless machine, using a 10Gb USB stick for the system and 2 mechanical drives for data. All installed without much problem, and the GUI OMV management is made easier with added plugins like OMV extras, Flash Memory and Shell-in-a-Box. The data drives are quickly beginning to get populated! So far so good. I can see and access the folders/files perfectly from Windows with SMB/CIFS and on my TV using DNLA. Works a treat!

However.........I hit a problem the other day maybe worth sharing. During the initial configuration of the filing systems using OMV GUI, I set a Quota limit (to around 100Gb for me as a User) on one of the data drives. Shortly later I decided to remove the limit, again in the GUI. All seemed fine and this episode was forgotten.

A couple of weeks later as I was transferring files from Windows 10 to the OMV folders using SMB/CIFS service I got a warning in Windows along the lines of "your file needs 2Gb and there isn't enough space on the destination drive". I could see there was still about 400Gb of storage left so no issue there. Everything in the GUI configs looked OK, including the Quota panel.

After a few bum steers from Google searches, I eventually I lifted the lid using the very handy Shell In a Box as a root user, and found using the quota command that the file system limit I initially set had in fact not been removed. So I used the setquota command to reset it to zero, i.e. removing the limit. Bingo! Remaining files in Windows continued to transfer to the OMV data drives again without problem.

However it leaves the question - what happened? Has anybody else found that using the Quota settings in the GUI are not getting translated across properly to the system config settings?

fop

p.s. I hit separate issue in file transfers - a network issue using an Atheros Ethernet card - separate post