• 2 Posts
  • 50 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle
  • You can host docker volumes over NFS, but the actual container images need to exist on a filesystem that supports overlay (which NFS does not) unless you want things to be slow as shit. And I really do mean miserably slow. A container image shared over NFS will take forever to spin up because it has to duplicate the entire container filesystem instead of using overlays, and then it’ll blow up your disk usage by copying all these files around instead of overlaying them. It’s truly unusable.





  • Just from a quick glance, you might want to check your client-side GET request: Ask yourself what happens when the file is larger than your packet buffer? Use the debugger or print statements to confirm if your expectations match reality. It might help to do some testing with a really tiny buffer (eg 5 bytes) so you can step through your 21 byte payload easily. What happens when your buffer is smaller than the DONE packet? If your implementation is correct then we would expect that even a 1 byte buffer should work in all cases.

    I see a similar code pattern in your server-side PUT request, so if you can solve it for one half, you should be able to fix both.








  • So many bad-faith arguments being made about this.

    Independent of any arguments about who asked for this to happen and why: A free software project always has the right to choose which contributors it trusts and which it doesn’t. I’ve seen no evidence that these people are banned from submitting patches due to their nationality. They’ve been remove from a particular role in the project due to political reasons. An organization is an inherently political entity.

    Remember when codes of conduct destroyed all of free software and nothing ever got built again? Me neither. It’s the same thing.






  • As someone who has owned enterprise servers for self-hosting, I agree with the previous comment that you should avoid owning one if you can. They might be cheap, but your longterm ownership costs are going to be higher. That’s because as the server breaks down, you’ll be competing with other people for a dwindling supply of compatible parts. Unlike consumer PCs, server hardware is incredibly vendor locked. Hell, my last Proliant would keep the fans ramped at 100% because I installed a HDD that the BIOS didn’t like. This was after I spent weeks tracking down a disk that would at least be recognized, and the only drives I could find were already heavily used.

    My latest server is built with consumer parts fit into a 2U rack case, and I sleep so much easier knowing I can replace any of the parts myself with brand new alternatives.

    Plus as others have said, a 1U can be really loud. I don’t care about the sound of my gaming computer, but that poweredge was so obnoxious that despite being in the basement, I had to smother it with blankets just so the fans didn’t annoy me when I was watching TV upstairs. I still have a 1U Dell Poweredge, but I specifically sought out the generation that still let you hack the fan speeds in IPMI. From all my research, no such hack exists for the Proliant line.




  • OneCardboardBox@lemmy.sdf.orgtoSelfhosted@lemmy.worldServer build for Family
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    9 months ago

    I’d recommend BTRFS in RAID1 over hardware or mdadm raid. You get FS snapshotting as a feature, which would be nice before running a system update.

    For disk drives, I’d recommend new if you can afford them. You should look into shucking: It’s where you buy an external drive and then remove (shuck) the HDD from inside. You can get enterprise grade disks for cheaper than buying that same disk on its own. The website https://shucks.top tracks the price of various disk drives, letting you know when there are good deals.