• 1 Post
  • 781 Comments
Joined 3 years ago
Cake day: June 12th, 2023
  • billwashere@lemmy.worldtomemes@lemmy.world•Living languageEnglish
    212·
    3 days ago

    ok here’s three examples of exactly what the meme is referring to:

    • “Awful” originally meant “awe-inspiring” or “full of awe,” but frequent use to mean “very bad” eventually became the standard modern meaning.

    • “Peruse” traditionally meant “to read carefully,” but common casual use to mean “to skim or browse” has become widespread enough that dictionaries now record both senses.

    • “Nimrod” started as the name of a skilled biblical hunter, but repeated ironic use as an insult (for example, in cartoons… “Bugs Bunny”) led to its accepted modern sense of “fool” or “idiot.”

    Language changes. Words mean what we say they mean since its all made up anyway.

  • billwashere@lemmy.worldtoSelfhosted@lemmy.world•Decreasing Certificate Lifetimes to 45 DaysEnglish
    92·
    10 days ago

    But can you imagine the load on their servers should it come to this? And god forbid it goes down for a few hours and every person in the world is facing SSL errors because Let’s Encrypt can’t create new ones.

    This continued shortening of lifespans on these certs is untenable at best. Personally I have never run into a situation where a cert was stolen or compromised but obviously that doesn’t mean it doesn’t happen. I also feel like this is meant to automate all cert production which is nice if you can. Right now, at my job, all cert creation requires manually generating a CSR, submit it to a website, wait for manager approval, and then wait for creation. Then go download the cert and install it manually.

    If I have to do this everyday for all my certs I’m not going to be happy. Yes this should be automated and central IT is supposed to be working on it but I’m not holding my breath.

  • billwashere@lemmy.worldtoTechnology@lemmy.world•Don't throw away your old PC—it makes a better NAS than anything you can buyEnglish
    1·
    10 days ago

    I would think that right now the sweet spot for good used drives is between 4-8tb. Check out backblaze’s drive stats for some good info about failure rates for older drives.

    https://www.backblaze.com/blog/category/cloud-storage/hard-drive-stats/

    Yeah RAID 5 is fine (in ZFS terms it’s just called raidz or raidz1). You could also do something like raidz2 (which is essentially RAID6 with two parity drives). There is some newer stuff in TrueNAS called dRAID which does some interesting stuff with the spares. It’s kinda like old RAID5EE stuff if youre familiar with that. Just google it and read up on it.

    Safest bet on old hardware… in my opinion find some old enterprise level stuff somebody is upgrading out of. I get lots of hand-me-downs that way. This stuff is meant to run 24/7, keep running forever, and is usually upgraded before it’s really not useful to anyone. Word of warning, this stuff is generally not power efficient, or quiet for that matter. So I wouldn’t be running this in my bedroom. Well unless you’re cold 'cause your heater is broken and love lots of white noise :)

    As a hardware guy going on 20+ years let me offer some basic advice. If this data is important , which you mentioned it was, RAID is NOT backup. Have separate backups. Yes I know it’s expensive but hardware can and does fail. Sometimes irrecoverably. ZFS does a good job helping with this with snapshots and the ability to sync easily. For me just I follow the 3-2-1 rules. Yeah it’s kinda outdated but I’m old.

    The 3-2-1 rule is basically:

    • 3 copies

      • Primary data (on its own pool).
      • Local backup (on a separate ZFS pool, ideally on different hardware). This is where ZFS replication is useful. This built into TrueNAS.
      • Off‑site/cloud backup (replicated ZFS dataset or traditional backup tool like restic/Borg to cloud).

    • 2 different media

      • e.g., Primary on SSDs, backup on HDDs; or primary on local NAS, backup in cloud.

    • 1 off‑site

      • Replicate ZFS snapshots to a remote location (another site or cloud).

    Oh and one other thing. If you are using TrueNAS be mindful there are two flavors now, TrueNAS Core and TrueNAS Scale. The interfaces are slightly different but the main differences are:

    • TrueNAS Core is based on FreeBSD and is the older, more mature “classic NAS” platform, optimized for rock‑solid file serving with jails and VMs.

    • TrueNAS Scale is based on Debian Linux and is designed for “scale‑out” and hyperconverged use: clustering, containers, and modern virtualization on newer hardware.

    Hope this is useful….

  • billwashere@lemmy.worldtoTechnology@lemmy.world•Don't throw away your old PC—it makes a better NAS than anything you can buyEnglish
    2·
    11 days ago

    With TrueNAS yes, a sata card connected to a bare drive is the preferred way. I have done it differently with enterprise hardware and virtualization but it’s not really supposed to be done that way. And ZFS is not technically “RAID” in the classic sense, but it does implement its own RAID‑like redundancy (RAIDZ and mirrors) as part of an integrated filesystem and volume manager. There are also things you can do with faster NVME drives like SLOG, L2ARC, and SPECIAL vdevs to store pool metadata. But some of these can fail and wipe out all your data if you aren’t careful. So read a lot.

    Second hand drives are fine in my opinion as long as SMART is not reporting any immediate errors. Just assume you will have failures and have spares built into the zfs volume.

    I’m not an expert by any stretch but I have been doing this for 10 plus years so I have some experience.