• 0 Posts
  • 78 Comments
Joined 1 year ago
cake
Cake day: November 23rd, 2023

help-circle






  • No. Symlinks and hardlinks are two approaches to creating a “pointer to a file.” They are quite different in implementation, but at the high level:

    • Symlinks can point to other filesystems, hardlinks only work on the same filesystem.
    • You can delete the target of a symlink (or even create one that points at nothing), but a hardlink always points to a real file.

    In both cases, the only additional data used is the metadata used for the link itself. The contents of the file on disk are not copied.





  • No, but you’ll have much more overhead. I have a VM that hosts all Docker deployments which don’t need much disk space (most of them)

    This is a big point. One of the key advantages of docker is the layering and the fact that you can build up a pretty sizeable stack of isolated services based on the same set of core OS layers, which means significant disk space savings.

    Sure, 200-700MB for a stack of core layers seems small but multiply that by a lot of containers and it adds up.




    • When you’re trying to make it level and hit the studs with your fasteners, it’s much easier with a stick than a whole cabinet carcass.
    • Cleats make the cabinet easy to install and remove.
    • French cleats have a substantial amount of bearing surface and are extremely stable as a result, even without additional fasteners.
      • That said, for a cabinet I would probably still drive a screw from the inside through the back panel into the cleat to eliminate any chance of a strong bump from underneath knocking the cabinet off the cleat. You know, like when you drop that last m4 nut on the desk and it bounces into the corner and you have to reach over your project and soldering iron and cup of coffee to retrieve it and then stand up too quickly in triumph and bang your head off the underside of the cabinet…





  • Ultimately it’s a matter of personal choice and risk tolerance.

    The Z1 will be simpler and have larger capacity, but if you have a drive fail you’ll need to quickly get it replaced or risk having to rebuild/restore if the mirror drive follows the first one to the grave.

    Your Z2 setup right now can have two drives fail and still be online, and having a wider spread of power-on hours is usually a good thing in terms of failure probability.

    I manage a large (14,000±) number of on-site RAID1 arrays in various environments and there is definitely a trend for drives shipped at the same time to fail at roughly the same time. It’s common enough that we often intentionally swap drives out before shipping a new unit to the customer site.

    On my homelab, I’m much more tolerant of risk since I have trust in my 3-2-1 backup solution and if my NAS goes down it’s not going to substantially affect anything while I wait for a drive replacement.