Caveat: LVM does not have built-in snapshots like ZFS has.
How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
191–200 of 265 posts
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#192A friendly reminder since it's probably relevant: when's the last time you tested disaster recovery for your own setup? If you haven't verified recovering it, you don't have an offsite backup. I had a cloud backup (Backblaze B2, using rclone and encryption) for my home NAS. Some unlucky drive failures later, I was getting ready to recover from my Backblaze backup... and then I couldn't find/remember where I saved the…
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#193Earlier quoted context omitted.
For home usage, if you have backups raidz1 is fine (just do an incremental backup at the first sign of trouble). If you don’t have backups, then you probably shouldn’t be running a NAS in the first place.
In the Linux ISO community the math is different because none of the data is essential, however there is a lot of it. Backing it all up even one time to an off-site location would be a 2x expense for a hobby. So 3-2-1 is hard to justify. Instead the math can be different e.g. it's ok to lose some data but not all. Therefore you might prefer the unraid approach over zfs where losing more than parity doesn't kill the w…
I don't want to lose 26TB just for a mirror, and I have a spare 8TB USB HDD. I'm torn between unraid and just Debian, and I'm torn between just two separate devices and one RAID 1 partition one RAID 0
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#194If you use LVM you can have a similar pool of storage with 1GB RAM or even less, instead 8GB (ZFS requirement). Caveat: LVM does not have built-in snapshots like ZFS has.
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#195Earlier quoted context omitted.
Hey everyone, stop progress! Wolrah has decided that November 29, 2022 is as far as things should go. Because everyone knows before that day, there were no scams, every artist lived lavishly from commissions, and software was flawless and without any extraneous features.
There's a difference between standing in the rain and being hit by a tsunami, even if it's both just water.
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#196Earlier quoted context omitted.
smartmontools makes this trivial and can email you which might be better than beeping and lights if you’re not always near your server. I use that plus smartctl_exporter so I can do metrics and alerting off that.
smartmontools misses data corruption at the drive layer, as it trusts the drives to report faithfully. "In hashes I trust"
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#197If you use LVM you can have a similar pool of storage with 1GB RAM or even less, instead 8GB (ZFS requirement). Caveat: LVM does not have built-in snapshots like ZFS has.
LVM does have snapshots.
ZFS snapshots use Copy-on-Write differently and have no such allocated space limit. Thus, we can do interesting things like snapshotting a file system after an OS is installed, and then roll back to that snapshot upon an OS upgrade failure, or even clone a new file system from that snapshot to have a different copy of the OS.
Essentially, the nature of the snapshots are different in both.
[1] https://docs.redhat.com/en/documentation/red_hat_enterprise_...
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#198Earlier quoted context omitted.
> Not a great time price-wise to be building a NAS That under-states the matter. It is a terrible time, price-wise, to build a NAS. I'd almost rather have no AI whatsoever and have storage 1/10 the price of pre-AI times. (If there were a magical choice between having AI and significantly more expensive storage, and having no AI and some program to dump that investment money into getting and somehow leveraging signifi…
> I'd almost rather have no AI whatsoever and have storage 1/10 the price of pre-AI times. Almost? ALMOST!?!?! If you handed me a button that would make it like LLMs had never existed I'd be slamming that button so hard Sam Altman's clothes would spin around. Return memory and storage prices to normal, undo the sloppification of ~everything, remove all these annoying "features" that are so useful they have to force t…
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#199Earlier quoted context omitted.
> I'd almost rather have no AI whatsoever and have storage 1/10 the price of pre-AI times. Almost? ALMOST!?!?! If you handed me a button that would make it like LLMs had never existed I'd be slamming that button so hard Sam Altman's clothes would spin around. Return memory and storage prices to normal, undo the sloppification of ~everything, remove all these annoying "features" that are so useful they have to force t…
Hey everyone, stop progress! Wolrah has decided that November 29, 2022 is as far as things should go. Because everyone knows before that day, there were no scams, every artist lived lavishly from commissions, and software was flawless and without any extraneous features.
They (probably) don't want to stop progress (especially unqualified like this) in general. They'd like a world where LLMs didn't come to exist.
And whether LLMs are progress at all remains to be proven.
Re: How to Build a Minimal ZFS NAS Without Synology, QNAP, TrueNAS (2024)
#200Earlier quoted context omitted.
Fire, malware, accidental deletions, capricious RAID controller (pre-ZFS). And that’s only the stuff that happened to me. Add power surge, theft, correlation in SSD failures (eg power on counter overflow firmware bug), damaging the array while moving, etc.
Malware, accidental deletion, RAID controller issues - all things ZFS with snapshots are immune to. You can decide if the other worry you or not - the risk is not zero, but it may be acceptable. Your backups are all subject to similar issues.
[edit] also snapshots aren’t really workable for large files. Remux a movie file and now it occupies twice the space.