@jonathankoren @neurovagrant Yeah, and AFAICT they mostly support #btrfs, #ext2 / #ext3 / #ext4, #FAT32 and maybe #ExFAT in some cases where the vendor paid $$ per device to #Microsoft.

Mainline #Linux ≠ #Android #toybox / #linux!
As I've gutted most out of the kernel for #OS1337 myself...

@neurovagrant you're welcome...

AFAIK even "modern" #Windows Versions can handle #ext4 and #btrfs with the "Linux Subsystem for Windows" [correct name since it's Linux on Windows!]

@neurovagrant Because #Microsoft patented #NTFS and thus #Linux can't officially support it.

You can thank the assholes that patented it for that.

Also unless you #root your android and build a custom #Kernel with #FUSE support you can't use ntfs-3g.

Consider using #btrfs or #ext4 instead.

In each case, the system is creating and replicating snapshots regularly.

Most of the latency deltas you're seeing come from the snapshot/replication tasks. Without those, you do still get ZFS advantages—but not this catastrophically severe.

Note that #btrfs is displaying latencies two and sometimes THREE orders of magnitude higher than #ZFS across a disturbing amount of the range of results. This is not just an issue at the absolute fastest or slowest ends of the scale, this is... normality.

I'm probably never going to write the actual article I'd originally intended these charts for. But if you want to see the difference between latencies between #OpenZFS and #btrfs on an eight-drive system that's creating and replicating automated snapshots regularly, here ya go.

We're looking at fio random access, limited to (simultaneous) 8MiB/sec read and 23.0MiB/sec write. The system has eight 12TB Ironwolf rust drives, in four ZFS mirrors vs one eight-wide btrfs-raid1.

Since #btrfs doesn’t support ‘FALLOC_FL_INSERT_RANGE’ and ‘FALLOC_FL_COLLAPSE_RANGE’ that I need, I’m running #xfs and #ext4 on loop devices ontop of btrfs and doing local development and testing there. Feels a bit cursed, but it works.

My #btrfs video as promised long ago - https://youtu.be/FCgXYcIYDe0

Just a friendly reminder that 'btrfs send' does not include child subvols. .

#linux #btrfs

@dekkzz76 I'm interested, #bcachefs' first-class support of caching devices and encryption are particularly interesting.

The fact it adds that *without* adding #ZFS' flaws of mostly requiring devices all the same size and not coping well with downgrading (enterprise assumptions™) is also part of what interests me (these are essential features #btrfs provides).

I'm probably going to wait for #SQLite and other #databases to have time to implement what support they need for it.

The new #Slimbook laptop set-up adventure continues!

This time the main goal was to set up system roll-back using Btrfs for when (inevitably) I mess up the install.

https://matija.suklje.name/system-snapshots-wayland-vulkan

TL;DR:
• update your firmware
• #Btrfs + #Baloo = problem (& workaround)
• Btrfs snapshots – for system roll-back (& backups)
• tried #Vulkan & #Wayland
• some small cool tools I use

OK, it’s 4 AM – such a typical time to end an install :blobmelt:

But it is done …well, the basic install at least of my #EndeavourOS on #Slimbook (on #Btrfs in #LUKS).

I have to say, this was surprisingly painless, thanks to the #Calamares installer.

https://matija.suklje.name/first-steps-of-the-installation

TL;DR:

• password-protect your BIOS!
• Btrfs + LUKS was super easy
• using GNU #GRUB now, might change to #rEFInd later
• DPS is a thing I need to read more about

Awesome! So glad to see that #btrfs subvolume/compression support landed in #ImageBuilder! 🎉

https://github.com/osbuild/osbuild/pull/1312

My #Slimbook / new laptop adventure continues! And with it a new blog post:

https://matija.suklje.name/installation-plans-for-my-new-laptop

TL;DR:

• why I decided for #EndeavourOS on a #Btrfs #RAID-1 on two #LUKS encrypted SSDs and not something else
• how I intend to mitigate the challenges this combination brings with it
• how to leverage #Tmpfs to make your SSD live longer and make your browser much faster
• #Borg in a great backup tool
• #Wayland … I hope

@sci_photos Zu SuSE-Zeiten habe ich das regelmäßig genommen...
#btrfs habe ich tatsächlich auch schon genutzt und fand es sehr simpel und komfortabel.
Mit Journaling-FS kommt chkfs kam noch vor, mkfs braucht man nur 1x bei der Installation.
Wenn ich daran denke, wie lange eine #NTFS-Formatierung bei #NT4.0 gedauert hat. Oder auch bei #ext2...

#DailyStandup

Yesterday:
- So I think the gi-docgen HTML parser is finally bug-free? Fuzzer hasn't found any issues in a while.

Today:
- I saw that @orsinium published his #golang enum library (https://github.com/orsinium-labs/enum), so I took a peek at it and filed a couple minor PRs :)
- Work on improving the btrfs-rec rebuild-mappings algorithm #btrfs

After reading my article on the uptime of the old #NetBSD server, a long-time client called me to check on their internal backup server (#Linux #Ubuntu 16.04, ext4 on root and #btrfs on the data partition).

According to them, it's still running smoothly. This server is not accessible from the outside (only via SSH from the admin VLAN) and it performs backups by connecting via SSH to some company servers and downloading all the data. It's a secondary backup.

While the results might not be as impressive as the NetBSD server, they're still noteworthy:

root@backup004:~# uptime
11:26:39 up 1642 days, 23:53, 3 users, load average: 4,61, 4,79, 4,72

Installing #GarudaLinux for its preconfigured #linux #kernel, chiefly to avoid the hassle of setting up #udevrules with #OpenRGB. A nice bonus is the #zenkernel for additional performance, and the easy GUIs for a straightforward OS. #snapper utilizing the powerful #btrfs is a nice feature too. Overall it's a great OS and will keep me around for a while, until I'm inflicted with the inevitable urge to #distrohop again.

Got a mail today thanking and complimenting me for my old blog post about what to do when #btrfs suddenly runs out of space.
https://ohthehugemanatee.org/blog/2019/02/11/btrfs-out-of-space-emergency-response/

It's very gratifying to hear that this stuff helps people. I should make time to write more.

So, my btrfs RAID1 on 2 HDDs just died, no magic btrfs repar/check command work, HDDs are physically healthy (at least SMART says so).

Time to test my #backup.....

#linux #btrfs #wtf

TIL you can 'chattr +C' on a directory, and any newly created files written to that directory will inherit the attribute.

Nice and convenient for VM disk files on a btrfs filesystem.

(The C attribute disables copy-on-write.)

#btrfs