Bcachefs Merges New On-Disk Format Version For Linux 6.11, Working Toward Defrag

[kneekoo]

Ya want the GNOME 4 or KDE version of the GUI? Or maybe you'll want to wait for the spin that is coded in Qt6 ?

And there are development issues surrounding the Curses flavor of the GUI.

I would be thrilled to see a text-based defragger like the one in MS-DOS, but I guess a lot of people would prefer a graphical tool, which makes more sense for normies.

[oleid]

I'm almost 100% sure this is the "famous" 32-bit problem. AFAIK right now bcachefs can only work in 64 bits, not 32 bit libraries like steam.

Out of curiosity : what does the file system have to do with the bit length of userspace pointers? Would you elaborate, please?

[EvilPiePirate]

Out of curiosity : what does the file system have to do with the bit length of userspace pointers? Would you elaborate, please?

Userspace sometimes uses the inode number in interesting ways (e.g. hardlink detection), and if userspace expects it to be 32 bits and the filesystem is using 64 bits things break.

bcachefs uses 64 bit inode numbers by default because we use the high bits of the inode number for sharding by CPU, which is a big help on multithreaded workloads - but there is an option for 32 bit inode numbers.

[oleid]

Userspace sometimes uses the inode number in interesting ways (e.g. hardlink detection), and if userspace expects it to be 32 bits and the filesystem is using 64 bits things break.

bcachefs uses 64 bit inode numbers by default because we use the high bits of the inode number for sharding by CPU, which is a big help on multithreaded workloads - but there is an option for 32 bit inode numbers.

Ah, that makes sense, thanks! So it is rather a "filesystem breaks userspace" (well, misbehaving userspace) than a "userspace breaks filesystem". I assumed you were talking about the latter and was wondering how this was even possible.

[PuckPoltergeist]

Userspace sometimes uses the inode number in interesting ways (e.g. hardlink detection), and if userspace expects it to be 32 bits and the filesystem is using 64 bits things break.

bcachefs uses 64 bit inode numbers by default because we use the high bits of the inode number for sharding by CPU, which is a big help on multithreaded workloads - but there is an option for 32 bit inode numbers.

So all userspace must fail on ZFS, because they use 128bit

[man-walking]

Is there any not too technical page where I can follow news/advances about bcachefs development?
The main site bcachefs.org looks to me not up to date.
I would like to try bcachefs as a secondary volume for my Arch linux machine, but I don't know ATM how to safe it is

[lyamc]

Is there any not too technical page where I can follow news/advances about bcachefs development?

You're on it