Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • lyamc
    replied
    Originally posted by man-walking View Post
    Is there any not too technical page where I can follow news/advances about bcachefs development?
    You're on it

    Leave a comment:


  • man-walking
    replied
    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

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by EvilPiePirate View Post

    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

    Leave a comment:


  • oleid
    replied
    Originally posted by EvilPiePirate View Post

    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.

    Leave a comment:


  • EvilPiePirate
    replied
    Originally posted by oleid View Post

    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.

    Leave a comment:


  • oleid
    replied
    Originally posted by AndyChow View Post

    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?

    Leave a comment:


  • kneekoo
    replied
    Originally posted by NotMine999 View Post

    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.

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by AndyChow View Post

    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.
    Please tell us you're trolling

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by EvilPiePirate View Post

    No, it will not
    How could this work? These are two conflicting targets.

    Leave a comment:


  • geearf
    replied
    Originally posted by Mitch View Post

    That's one of my happy memories.

    I'd run CCleaner to clear files, a registry cleaner called Registry Clean Expert, and then leave VoptXP running (a visual defragmenter) before heading to highschool or before bed. And when I got back, I'd get to see my squeaky-clean Windows XP, run a ram optimizer (can't recall which ones), and play Morrowind, Spellforce, Maplestory, and Gothic.

    I had a screaming fast Pentium single-core CPU, a revolutionary Geforce FX 5500, and future-proof 1 GB of that sexy DDR2 RAM. And I squeezed more juice out of this monster with RivaTuner.
    You missed out, defrag as a screen saver was it!

    Leave a comment:

Working...
X