Jump to content
  • 6.12.13 Extremely slow smb writes


    Spokz
    • 6.12.14 Solved Urgent

    Writing from a Windows 11 PC with all the latest updates installed to a smb share results in unusable smb write speed of kbs. I have tried with windows explorer that takes minutes just to calculate and other copy apps. Tried writing to other shares and removing any smb extras. Issue was fixed as soon as i downgraded to 6.12.11. 

     

    I didn't test the smb write performance using other OS's.

     

    Hopefully other Windows users can replicate the issue.

    • Upvote 6



    User Feedback

    Recommended Comments



    mtikhov

    Posted

    37 minutes ago, JorgeB said:

    This is a kernel issue, but there's no fix yet for kernel 6.1, only for newer LTS kernels.

    Fresh update on kernel defect

    Quote

     

     

    • Like 1
    BigJimsBoat

    Posted (edited)

    EDIT: In my case, the update just messed up the ethernet settings. I am running unRAID as a Proxmox VM. The VirtIO network driver was messed up. Switched to Intel e1000e and I'm getting 2.5GBE all fine. Not Lime Tech's fault!

     

    Upgraded to Version 6.12.13 today. Everything is 2.5GBE. Before update, transfers were approx 2.5gbe from Windows 10 to UnRAID (SSD Cached share) and around 1.1Gbps down (always had i225 issues on the Windows Machine).

     

    Upgraded to 6.12.13 and here's what I get:

    Copying from Windows to UnRAID SSD Cache: says "Calculating" and it just stays there. If I wait, it times out and there's a file on the server that's the same size, but corrupted. Same if I copy to a share directly on the Array.  While it's stuck on "Calculating" I cannot close the copy window. Even browsing folders on the server slowed to a crawl.

     

    I set all array drives to never sleep. No Drive actions are running. Disabled Docker and VM.

     

    Pretty unusable atm.

     

     

    Edited by BigJimsBoat
    • Like 1
    zellux

    Posted

    Same here. Extreme slow transfer speed and responsiveness when access samba from my Windows 11 PC. It works well under Mac though. After downgrading to 6.12.11, the issue went away.

    BigJimsBoat

    Posted

    In my case, all slowness issues (Windows explorer locking up during transfers) in unRiad came down to these:

     

    1. My unRAID is in a VM with an HBA passed through...  I had the nic on the VM set to virtio. When I switched to intel e1000 all network issues pretty much stopped. Every VM on your stack... Check the network emulation. 

    2. I tested, retested and pulled my hair out about slowness and everything locking up, until I installed Diskspeed and tested my SSD cache drives and one kept showing slow writes, very slow.  No errors. In a mirror, raid, or parity situation one slow drive screws up the entire server and will ruin your day. 

     

    Next, check Windows. Update network drivers and check speeds copying to other devices 

    adamrgolf

    Posted

    They added a note to the known issues section of the changelog when updating:

     

    Quote

     

    Windows VMs should use the VirtIO-net driver

    Due to a kernel regression, there is significant performance degradation for any outgoing transfer from a Windows VM using the VirtIO network driver. The workaround is to switch to the VirtIO-net driver. This should be resolved in a future release.

     

     

    • Like 1
    tjb_altf4

    Posted (edited)

    On 8/29/2024 at 10:13 PM, BigJimsBoat said:

    EDIT: In my case, the update just messed up the ethernet settings. I am running unRAID as a Proxmox VM. The VirtIO network driver was messed up. Switched to Intel e1000e and I'm getting 2.5GBE all fine. Not Lime Tech's fault!

     

    Upgraded to Version 6.12.13 today. Everything is 2.5GBE. Before update, transfers were approx 2.5gbe from Windows 10 to UnRAID (SSD Cached share) and around 1.1Gbps down (always had i225 issues on the Windows Machine).

     

    Upgraded to 6.12.13 and here's what I get:

    Copying from Windows to UnRAID SSD Cache: says "Calculating" and it just stays there. If I wait, it times out and there's a file on the server that's the same size, but corrupted. Same if I copy to a share directly on the Array.  While it's stuck on "Calculating" I cannot close the copy window. Even browsing folders on the server slowed to a crawl.

     

    I set all array drives to never sleep. No Drive actions are running. Disabled Docker and VM.

     

    Pretty unusable atm.

     

     

    Yesterday I had to upgrade one of my Unraid servers running under Proxmox and hit the same issue, but I then got hit with new issues (call traces etc) with E1000.
    Ended up using vmxnet3 and its been stable overnight.

    The patch for this is out in the wild now, hopefully I'll just upgrade to unraid 7 (with a newer kernel) and be done with the issue.

    Edited by tjb_altf4
    • Like 2
    tjb_altf4

    Posted (edited)

    Can't test myself yet, but it looks like 7.0.0-beta.3 has a kernel version (6.6.52-Unraid) with the virtio patch that seems to address the root of the problem.
    https://lwn.net/Articles/990767/

    Edited by tjb_altf4
    • Upvote 1
    pandan888

    Posted

    Just adding my voice to the crowd here. Also had rock bottom SMB transfer speeds. Downgraded to 6.12.11 and back to normal.

    hermannp

    Posted

    I Have the same problem!! Also had rock bottom SMB transfer speeds. Downgraded to 6.12.11 and back to normal!!

    JorgeB

    Posted

    See the release notes, you need to change the virtio driver to virtio-net for example.

    johnsanc

    Posted

    Does 6.12.14 fix this issue? I do not want to use virtio-net since the performance is poor compared to virtio.

    • Like 2
    WackyWRZ

    Posted

    28 minutes ago, johnsanc said:

    Does 6.12.14 fix this issue? I do not want to use virtio-net since the performance is poor compared to virtio.

    Good question, it should be - the kernel bug was fixed 2 months ago.

     

    Would be worth adding to the release notes if it does, I've been on 6.12.11 because virtio-net wasn't a good workaround.

    • Upvote 2
    JorgeB

    Posted

    50 minutes ago, johnsanc said:

    Does 6.12.14 fix this issue?

    Yep.

     

     

    mtikhov

    Posted

    18 minutes ago, WackyWRZ said:

    Good question, it should be - the kernel bug was fixed 2 months ago.

     

    Would be worth adding to the release notes if it does, I've been on 6.12.11 because virtio-net wasn't a good workaround.

    Unraid 6.12.13 has Linux kernel 6.1.106

    Unraid 6.12.14 has Linux kernel 6.1.118

    SO there is a chance that bug was fixed in updated kernel, but I couldn't find definitive prove that updated Linux kernel incudes fix for that bug

     

    • Like 1
    JorgeB

    Posted

    Changed Status to Retest

    Changed Version to 6.12.14

    • Like 1
    JorgeB

    Posted

    This is issue is fixed for me in 6.12.14, please retest.

    • Like 2
    johnsanc

    Posted

    Confirmed fixed for me. Thanks!

    • Like 2
    Starfiresg1

    Posted

    Switched back all my Windows-VMs to virtio after the upgrade yesterday. No issues so far 👍

    • Like 1
    bjmi

    Posted (edited)

    On 11/27/2024 at 7:05 PM, JorgeB said:

    This is issue is fixed for me in 6.12.14, please retest.

    I can also confirm that my Windows 11 VM using virtio drivers works with 6.12.14 smoothly again.

     

    On 11/27/2024 at 6:40 PM, WackyWRZ said:

    Would be worth adding to the release notes if it does, I've been on 6.12.11 because virtio-net wasn't a good workaround.

     

    This is actually a very good idea as this bug affects several people. You could even link this thread in the changelogs.

     

     

    Edited by bjmi
    • Like 1
    JorgeB

    Posted

    Changed Status to Solved




    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...