[PSA] Swapping your Deck's filesystem to Btrfs is easy to do, and can give you more space for free
[PSA] Swapping your Deck's filesystem to Btrfs is easy to do, and can give you more space for free
Inject a payload into SteamOS 3.0 to convert the /home partition from ext4 to btrfs. Also allows mounting btrfs formatted sd cards and forces new sd card formats...
Btrfs is a filesystem (like FAT, NTFS, and ext4), but has some distinct advantages:
-
Increased storage - thanks to compression and file deduplication, Btrfs can save you considerable amounts of storage. I have 517G of files on my Deck's SSD, but it only uses up 410G of storage to hold those files. Compressing your filesystem can also shorten load times, especially for slower memory devices like the SD card.
-
Snapshotting - save snapshots of the file system and easily roll back if there's a problem.
Converting to Btrfs is easy to do, and doesn't require having you to resetup/reconfigure your deck. The linked gitlab project will do the conversion, keep all your existing files and settings, and set all the Btrfs configurations for you. The file conversion will persist through updates, and it will setup automatic deduplication of files on the drive. It also allows the Deck to automatically mount Btrfs converted SD cards, and to format new cards in the same format.
Only potential downside I know of is that Btrfs is case sensitive, where the default ext4 on the Deck uses casefolding. Basically this means that Btrfs will treat File.txt and file.txt as two different files. I've never run into any issues with this, but I've heard it can cause issues with some specific mods that inconsistently capitalize their files. There's also always some risk whenever you make dramatic changes to your filesystem, but I haven't really heard of anyone having problems with this. You do have to make sure you have at least 10-20% of your storage free (and a min of 10-20GB free for smaller drives) to make sure it has room for the conversion.
Overall I've been using Btrfs for over 6+ months on my deck, and it's been great. I highly recommend it. I'm not an expert on it, but I'll do my best to answer any questions on it.
As someone who fell for the "Swap over to Fat32 and you'll gain so much space" back in the day, I feel like I need to point out to newbies here, anything done to your file system has quite a bit of risk. Things can go wrong in a way that are unrecoverable unless you full reset your device. I'm not saying this project is unstable, but there is a high amount of risk involved with this.
If you decide to do this, back up all data that you may need saved and then mentally prepare that you may ultimately end up resetting your device in the end. These are real possibilities when messing with file systems.
The real risk is losing a bit of time with this. Since everything is backed up anyways, the data is just a restore away.
If you don’t have a backup, that's the risk and has nothing to do with this procedure.
For the Steamdeck the risk is even less, since Steam backs up savegames automatically and the games can be re-downloaded at any point for free (except for Unity developers, who have to pay 20 cents for this).
[This comment has been deleted by an automated system]
Yeah, Linus Torvalds has been pushing for ECC RAM everywhere for just this reason.
The filesystem metadata comes with 2 copies that can heal each other, and Copy-on-Write protects against power loss. The filesystem itself should be bulletproof.
I feel like people reporting data loss on BTRFS are unaware that at least BTRFS is actually measuring the data loss. Bitrot is not rare, especially with how big our drives are getting. If you care about your data it should be backed up and/or RAIDed. Ext4 has no idea if your data is still intact - that's not the same as no data loss.
I know this gitlab project sets some downloading/temp folders to have COW disabled, possibly for this very reason.
I noticed this guide recommends
compress-force=zstd, which sets the ZSTD compression to level 3. There's a BTRFS benchmark and ZFS benchmark of the ZSTD levels which can give a rough idea of how ZSTD performs for transparent filesystem compression. Note that almost all of ZSTD's compression gains happen starting at level 1, and levels after that have very minor improvements.Also keep in mind that ZSTD levels only affect how long it takes to write new data to the filesystem. ZSTD is somewhat unique as a compression algorithm in that as you increase compression effort, the decompression effort stays the same. You could compress everything with level 15 and it will decompress just as fast as level 1 (~generally). Setting higher ZSTD levels could arguably make more sense for a gaming drive because the data is usually write-once, read-many. I don't know at what level the Steam Deck CPU will start limiting your I/O though.
BTRFS compression is enabled per-file, so you can change ZSTD levels at any time and old data will still be compressed with your previous algorithm. To recompress using a new level, change your
/etc/fstab/ZSTD level and remount the partition, then run a defrag to poke the data into recompression.Here's one sharp edge: defrag will unshare file contents so sometimes it's not just feasible to do it.
Run
duperemoveon the partition after defragging to get those reflinks back. Duperemove is usually a good idea anyway unless you're running on a HDD - reflinks are almost identical to fragmentation in nature so you might prefer to have less fragmentation on a mechanical drive instead of easy de-duping.
I've tried btrfs twice, and both times I regretted it. I also regret XFS, and reiserfs, but I had to do that because ext2 could just not deal with the very large, deep and multitudinous number of files I had to manage. Oh and jfs, also regret.
You should try ZFS (not on the SD, though). It’s pretty solid and used in NAS very often.
I've had great luck with xfs and zfs, but btrfs has lost data for me more than once.
Compressing your filesystem can also shorten load times
At the cost of adding pressure to the already limited CPU.
To get around the case folding issue you could mount your steamapps/common folder as a loop device with ext4 with case folding support. The virtual device should follow the compression settings without too much issue but deduplication won't be an option and snapshots may be larger.
I’m a big fan of BTRFS, I use it in my desktop and laptop but I'd be curious if the compression is worth the battery & compute trade off. I’m not sure how much battery/compute is used day to day to decompress and compress files read and written. But I guess it depends on which is more valuable, battery or storage.