this post was submitted on 05 Aug 2023
119 points (97.6% liked)
Linux
47730 readers
966 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This might be controversial here. But if reliability is your biggest concern, you really can't go wrong with:
You want something with patrol read, supercapacitor- or battery-backed cache/NVRAM, and a fast enough chipset/memory to keep up with the underlying drives.
LVM with snapshots
Ext4 or XFS
A basic UPS that you can monitor with NUT to safely shut down your system during an outage.
I would probably stick with ext4 for boot and XFS for data. They are both super reliable, and both are usually close to tied for general-purpose performance on modern kernels.
That's what we do in enterprise land. Keep it simple. Use discrete hardware/software components that do one thing and do it well.
I had decade-old servers with similar setups that were installed with Ubuntu 8.04 and upgraded all the way through 18.04 with minimal issues (the GRUB2 migration being one of the bigger pains). Granted, they went through plenty of hard drives. But some even got increased capacity along the way (you just replace them one at a time and let the RAID resilver in-between).
Edit to add: The only gotcha you really have to worry about is properly aligning the filesystem to the underlying RAID geometry (if the RAID controller doesn't expose it to the OS for you). But that's more important with striping.
Oh great another single point of failure. Seriously, don't use raid cards. With ZFS, there's no corruption on power loss. It's also self healing.
How many hardware RAID controllers have you had fail? I have had zero of 800 fail. And even if one did, the RAID metadata is stored on the last block of each drive. Pop in new card, select import, done.
1/1, irrecoverable array as that particular card was no longer available at time of failure failure Problems that don't exist with ZFS
I am sorry that you had to personally experience data loss from one specific hardware failure. I will amend the post to indicate that a proper hardware RAID controller should use the SNIA Common RAID DDF. Even mdadm can read it in the event of a controller failure.
Any mid- to high-tier MegaRAID card should support it. I have successfully pulled disks directly from a PERC 5 and imported them to a PERC 8 without issues due to the standardized format.
ZFS is great too if you have the knowledge and know-how to maintain it properly. It's extremely flexible and extremely powerful. But like most technologies, it comes with its own set of tradeoffs. It isn't the most performant out-of-the-box, and it has a lot of knobs to turn. And no filesystem, regardless of how resilient it is, will ever be as resilient to power failures as a battery/supercapacitor-backed path to NVRAM.
To put it simply, ZFS is sufficiently complex to be much more prone to operator error.
For someone with the limited background knowledge that the OP seems to have on filesystem choices, it definitely wouldn't be the easiest or fastest choice for putting together a reliable and performant system.
If it works for you personally, there's nothing wrong with that.
Or if you want to trade anecdotes, the only volume I've ever lost was on a TrueNAS appliance after power failure, and even iXsystems paid support was unable to assist. Ended up having to rebuild and copy from an off-site snapshot.