Learn More
Resend Email
7
12bitfloat
2y

Why do SAMBA network drives have to suck this much? Yeah I understand that compiling to a network drive is probably a bad idea just for performance reasons alone but can't you at least not fuck with my git repo?

$ git gc
Enumerating objects: 330, done.
Counting objects: 100% (330/330), done.
Delta compression using up to 24 threads
Compressing objects: 100% (165/165), done.
Writing objects: 100% (330/330), done.
Total 330 (delta 177), reused 281 (delta 151), pack-reused 0
error: unable to open .git/objects/7e: Not a directory
error: unable to open .git/objects/7e: Not a directory
fatal: unable to mark recent objects
fatal: failed to run prune

$ git gc
error: unable to open .git/objects/00: Not a directory
fatal: unable to add recent objects
fatal: failed to run repack

$ git gc
Enumerating objects: 330, done.
Counting objects: 100% (330/330), done.
Delta compression using up to 24 threads
Compressing objects: 100% (139/139), done.
Writing objects: 100% (330/330), done.
Total 330 (delta 177), reused 330 (delta 177), pack-reused 0
Removing duplicate objects: 100% (256/256), done.
error: unable to open .git/objects/05: Not a directory
error: unable to open .git/objects/05: Not a directory

rant

samba

smb

wtf

git
Favorite
Ranter
Comments
  • 2
    2y
    umm.. somethings wrong with your installation. there shouldn't be file content related issues, speed maybe but thats all
  • 1
    2y
    i was running samba flawlessly over 6 years at two different jobs to save things to network drives and never had any issues with programs accessing files or modifying them unless my permissions were off on the folders.
  • 1
    2y
    @AvatarOfKaine I second this.

    My NAS is mounted samba and I have no problems doing heavy read/write against it.

    I have saturated my 1gig Ethernet before whilst doing said operations.

    Check your network saturation. If it's not 60-100% utilized for long periods of time your drive might be dying.
  • 2
    2y
    My nas is also connected via samba. It works well when it works, but sometimes it’s just not there and nothing I do will change that. No idea why.
  • 5
    2y
    Samba is just the software.

    The protocol is SMB, original CIFS.

    The interesting part is which settings you use, especially version of SMB protocol.

    A network protocol isn't just the definition of how to transmit data - it has to take care of an *insane* amount of fuckity behind the scenes.

    This goes especially for the 3 dreaded sisters of apocalypse, as I'd like to call them:

    ACL / permissions
    Authentication
    FS Locking

    FS Locking is most likely the problem part that you have.

    GIT and any other tool relies on the FS, that is enumerated / emulated by the network protocol SMB, to properly sync changes to the disk.

    Depending on defaults, this might be not properly configured or disabled for speed....

    I'd highly rate to read the latest doc on samba.org and not trust ShitOverflow. If you could determine the version of samba and post the configuration (e.g. testparm) then someone might help.
  • 1
    2y
    I think Samba is pile of overcomplicated trash. If NFS is good enough for you, use that instead.
  • 1
    2y
    @WildOrangutan maybe worth mentioning that windows has NFS v4 support since V10 if I remember correctly.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment