Conversation
Notices
-
Embed this notice
Hyolobrika (hyolobrika@social.fbxl.net)'s status on Tuesday, 01-Oct-2024 20:29:23 JST Hyolobrika Who here has used btrfs recently?
Does it work well?-
Embed this notice
翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Tuesday, 01-Oct-2024 20:29:18 JST 翠星石 @Hyolobrika For laptop use you want either ext4 or f2fs, depending on if the laptop has a HDD or SSD.
Btrfs doesn't offer any real advantage over ext4 unless you want to do RAID. -
Embed this notice
Hyolobrika (hyolobrika@social.fbxl.net)'s status on Tuesday, 01-Oct-2024 20:29:19 JST Hyolobrika I'm setting up a laptop, not a server.
I ask because the OpenSUSE installer had it selected by default. I'm not sure whether to go with that or Arch though. -
Embed this notice
tyil (tyil@fedi.tyil.nl)'s status on Tuesday, 01-Oct-2024 20:29:22 JST tyil @Hyolobrika@social.fbxl.net It seems to perform worse than #ZFS for me, storing large volumes of data and for databases (PostgreSQL). However, for a very large number of smaller files (tens of thousands, under 4KiB) it seemed to perform slightly better and took slightly less space on-disk to store it.
In practice, it works "okay" enough to use for various setups, but I wouldn't trust it for serious large-volume storage unless you have very rigorous backups. I've seen it fuck up too often to trust that well. Be sure to avoid #BTRFS' raid 5/6 at all costs, I haven't heard much problems about their other raid options. -
Embed this notice
翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Tuesday, 01-Oct-2024 20:58:22 JST 翠星石 @vhns F2FS is designed for flash memory that is managed, like SD Cards, flash drives or SSD's - it's designed to reduce the amount of writes, while also increasing speed.
Unmanaged flash needs a filesystem like UBIFS. -
Embed this notice
Vitor Hugo (vhns@yuga.surf)'s status on Tuesday, 01-Oct-2024 20:58:23 JST Vitor Hugo @Suiseiseki @Hyolobrika isn't F2FS exclusively thought for devices where there isn't an abstraction over the flash memory? i.e not the case for SSDs. -
Embed this notice
feld (feld@friedcheese.us)'s status on Wednesday, 02-Oct-2024 06:01:48 JST feld @Hyolobrika @Suiseiseki changes which affect filesize may not cause fragmentation but it's not guaranteed, and on a CoW filesystem with low space the changes inevitably lead to fragmentation
whereas on a traditional filesystem it's possible that if the file size is not changing the data could just be changed in place.Another Linux Walt Alt likes this. -
Embed this notice
Hyolobrika (hyolobrika@social.fbxl.net)'s status on Wednesday, 02-Oct-2024 06:01:49 JST Hyolobrika Doesn't copy-on-write make it use space more efficiently? -
Embed this notice
翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Wednesday, 02-Oct-2024 22:47:11 JST 翠星石 @Hyolobrika CoW uses space less efficiently, as you often end up with 2 copies of the same file, although it's useful in the case where the power goes off just as the new version is being written - the old version of the file can be recovered, rather than the file ending up corrupted.
-
Embed this notice