87
What Filesystem?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Jul 2023
87 points (91.4% liked)
Linux
48654 readers
1473 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
O use ext4 at home and in servers that are not SLES HANA DB ones.
On SLES HANA servers I use ext4 for everything but the database partitions, for which SAP and SUSE support and recommend XFS.
In a few occasions people left the non-db partitions as the default on SUSE install, btrfs, with default settings. That turned out to cause unnecessary disk and processor usage.
I would be ashamed of justifying btrfs on a server for the possibility of undoing "broken things". Maybe in a distro hopping, system tinkering, unstable release home computer, but not in a server. You don't play around in a server to "break things" that often. Linux (differently from Windows) servers don't break themselves at the software level. For hardware breakages, there's RAID, backups, and HA reduntant systems, because if it's a hardware issue btrfs isn't going to save you - even if you get back that corrupted file, you won't keep running in that hardware, nor trust that "this" was the only and last file it corrupted.
EDIT: somewhat offtopic: I never use LVM. Call me paranoid and old fashioned, but I really prefer knowing where my data is, whole.
Facebook was using btrfs for some usecases. Not sure what you mean by breaking things?
Most comments suggesting btrfs were justifying it for the possibility of rolling back to a previous state of files when something breaks (not a btrfs breakage, but mishaps on the system requiring an "undo").
Ah, I see. While that use may be a good plan for home server, doing that for production server seems like a bandaid solution to having a test server and controlling deployed changes very carefully.
Exactly. A waste of server resources, as a productions server is not tinkerable, and shouldn't "break".