Originally posted by cynic
View Post
Announcement
Collapse
No announcement yet.
Casefolding For Bcachefs File-System Posted
Collapse
X
-
- Likes 3
-
Originally posted by ireri View Post
Yes, I do have a link, but I don't believe you could be genuinely interested, as searching for it is as easy as looking for "debian btrfs" in the engine of your preference and hitting the first result.
And you are right on the kernel version while it can be old for some, you must realize that it actually isn't for some environments;
- Likes 1
Comment
-
Originally posted by WereCatf View Post
I haven't had Btrfs wreck any data in a long, long time now, but I can make Btrfs hard crash quite easily on 5.15 under Ubuntu 22.04 LTS. A hard crash at the filesystem level is still pretty bad, regardless of whether any data gets wrecked or not, IMO.
- Likes 1
Comment
-
Originally posted by oleid View Post
How can you make it crash easily?
The system would work just fine during my daily tasks but would crash during a system upgrade. I guess the high number of reads and writes across the disk, combined with not having enough power, made the disk controller or whatever fail. Anyway, the end-result was a kernel panic with an error message related to the filesystem / Btrfs. There would be lots of zero-sized files, and my only way to recover was reinstalling packages on top the existing OS. (Which on Arch is pretty easy but still takes some time.)
I'm not blaming Btrfs, as that was likely a physical device fault, but it sure did look like a Btrfs failure when overlooking the circumstances.Last edited by curfew; 14 August 2023, 01:03 AM.
Comment
-
Originally posted by geerge View PostUnless I'm missing something the reason some games may crash on btrfs is precisely because btrfs doesn't do case folding, if the game is sloppy with path resolution it can't find files then shits itself. More microsoft baking a ticking compatibility timebomb into ntfs than anything btrfs has done wrong.
According to Wikipedia, there are older OSes/filesystems that are also case insensitive. Namely DECTape (and also Level-D, RT-11 etc) for PDP computers since 1964 and ODS-1 (and various -2, -5 etc) for PDP-11 and later on the VMS operating system since 1975. Bill Gates probably designed the FAT filesystem with them in mind.
Nowadays we take ASCII with uppercase and lowercase letters for granted but in the earliest days, the Morse code for telegraph is case insensitive.
Comment
-
Originally posted by brucethemoose View Post
F2FS compression does not save space, unless you manually make the compressed files immutable.
Also it has a relatively short file extension limit... I can't remember what it is exactly, as its not documented, and I had to find it in the source when I ran into it.
As for the crashes, some games are unhappy without casefolding (which is on by default in Windows). But this may not be the issue, as its not enabled in ext4 by default, and IIRC proton takes care of it anyway.Last edited by stormcrow; 14 August 2023, 01:09 AM.
Comment
-
Originally posted by oleid View Post
How can you make it crash easily?
- Likes 3
Comment
-
Originally posted by Britoid View PostThere's not any reliability problems with btrfs outside of raid 5/6, iirc the steam desk uses btrfs for the root fs but ext4 for the game data partition.
Some games however, don't run on XFS/btrfs and want an ext4 fs. It's also not the fastest FS right now
I'm even getting a lot of mileage out of btrfs on my desktop thanks to winbtrfs making it probably the best solution for dual-booters to share data between Linux and Windows, I grabbed a cheapo 6TB Seagate drive for the vast majority of games that don't really benefit from fast storage on which I've made two subvolumes, one for Linux and one for Windows, so both Windows and Linux think they've got completely unique installs of the same games despite dedupe ensuring minimal redundant data is actually being stored and additionally I have a 2TB Toshiba drive which I use for the user libraries (ie. The "Documents", "Music", "Pictures", "Videos" folders in /home/username and in Windows' user folder) once again shared between both OS' and has snapshotting enabled because that can be so bloody handy for those kinds of files. Other than that, I just use F2FS for my SSDs.
Originally posted by WereCatf View PostUse mergerfs to combine a couple of Btrfs disks, then point Radarr at it and BOOM -- dmesg shows a crash in the Btrfs module within the kernel and the system has to be hard-rebooted, because no normal filesystem operations work anymore. Another way of doing it is with LXD, but it's a bit lengthier process, so I can't be arsed to go through it here.
Comment
-
Originally posted by Democrab View Post
Out of curiosity, if you're only combining btrfs formatted disks wouldn't you just btrfs' inbuilt JBOD handling rather than MergerFS? Does MergerFS have additional features you're using or is there a drive with an alternative fs there?
EDIT: Now that I think about it, I'm unsure how Btrfs JBOD-like handles files that don't fit on a single disk, like e.g. that disk is getting full and there's no room to hold the full file. Does it spread the file over multiple drives, then? Mergerfs handles it so that each and every file is fully on a single drive, so you can't lose files due to them being spread over multiple drives. If Btrfs doesn't do that, then that's a big plus for mergerfs in such a scenario.Last edited by WereCatf; 14 August 2023, 05:56 AM.
Comment
-
Originally posted by WereCatf View Post[...]
EDIT: Now that I think about it, I'm unsure how Btrfs JBOD-like handles files that don't fit on a single disk, like e.g. that disk is getting full and there's no room to hold the full file. Does it spread the file over multiple drives, then? Mergerfs handles it so that each and every file is fully on a single drive, so you can't lose files due to them being spread over multiple drives. If Btrfs doesn't do that, then that's a big plus for mergerfs in such a scenario.
1) SINGLE (that is the one used in your link), in this profile each block-group (which is the allocation unit of btrfs) is allocated to the disk with the most free space. If you have two disk of the same size, the first block group is allocated on the first disk, the second block-group on the second disk, the third block group on the first disk... So a file may span different disk even if the filesystem is near empty.
2) RAID0, in this profile the data is spread over the disk in 64kb unit (i.e. the first 64kb is write in the first disk, the second in the second and so on)...
In both the cases, there is no guarantee that the filesystem survives to the lost of a disk.
Comment
Comment