shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

271
active users

#btrfs

3 posts3 participants0 posts today
The Last Psion | Alex<p>OK, riddle me this, <a href="https://oldbytes.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> (specifically <a href="https://oldbytes.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ArchLinux</span></a>) fans.</p><p>You can use <a href="https://oldbytes.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZFS</span></a> and <a href="https://oldbytes.space/tags/btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>btrfs</span></a> on root to create snapshots before updating the OS. But you can't snapshot EFI, because that's on a separate FAT32 partition.</p><p>So what happens if you run an update (<code>pacman -Syu</code> in this case) that includes a kernel update, and something goes wrong? The version of the kernel in the EFI partition will be newer than the modules in the snapshotted <code>/usr/lib/modules</code>. That's surely going to cause an issue, right?</p><p>From memory (it's been over 15 years), Gentoo can have multiple versions of the same kernel installed at once. But Arch only allows one version of any package at one time.</p>
Thorsten Leemhuis (acct. 1/4)<p>Highlights from the main <a href="https://hachyderm.io/tags/btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>btrfs</span></a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> 6.17[1]:</p><p>A number of usability and feature updates, scattered performance improvements and fixes. Highlight of the core changes is getting closer to enabling large folios (now behind a config option).</p><p>[…] </p><p>Performance improvements:</p><p>- caching of lookup results of free space bitmap (20% runtime improvement on an empty file creation benchmark)</p><p>- accessors to metadata (b-tree items) simplified and optimized, minor improvement in metadata-heavy workloads</p><p>- readahead on compressed data improves sequential read</p><p>- the xarray for extent buffers is indexed by denser keys, leading to better packing of the nodes (50-70% reduction of leaf nodes)</p><p>[…]</p><p>[1] <a href="https://git.kernel.org/torvalds/c/f92b71ffca8c7e45e194aecc85e31bd11582f4d2" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">git.kernel.org/torvalds/c/f92b</span><span class="invisible">71ffca8c7e45e194aecc85e31bd11582f4d2</span></a></p><p><a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxKernel</span></a></p>
argv minus one<p>I wonder if <a href="https://mastodon.sdf.org/tags/btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>btrfs</span></a> will ever have per-subvolume profiles.</p><p>This would, among other things, allow one to have a swap file on a RAID array. Just add a subvolume with a non-RAID profile, and you can put a swap file on it.</p><p><a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a></p>
Andreas Gohr<p>I guess it's time to finally decide (currently leaning towards 1)...<br><br><a href="https://fedi.splitbrain.org/tags/nas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nas</span></a> <a href="https://fedi.splitbrain.org/tags/btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>btrfs</span></a> <a href="https://fedi.splitbrain.org/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zfs</span></a></p>
Bhante Subharo ☸️<p><span class="h-card" translate="no"><a href="https://tooting.ch/@frox" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frox</span></a></span> I tried <a href="https://c.im/tags/Waydroid" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Waydroid</span></a>, but disliked it because the packaging was so poor. There was no uninstall to speak of. I wish I would have had a <a href="https://c.im/tags/BTRFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BTRFS</span></a> snapshot to roll back, as a means of uninstallation.</p>
Alejandro Baez<p>I'm getting the itch of building my next linux install using <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://fosstodon.org/tags/confext" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>confext</span></a> and <a href="https://fosstodon.org/tags/sysext" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysext</span></a>. 😎 </p><p>Basic point, memory of <a href="https://fosstodon.org/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ansible</span></a> keeps getting further. 😅 Can build out <a href="https://fosstodon.org/tags/btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>btrfs</span></a> subvolumes that are mounted read only. No modification of the /usr or even /etc necessary.</p><p><a href="https://man.archlinux.org/man/systemd-confext.8.en" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">man.archlinux.org/man/systemd-</span><span class="invisible">confext.8.en</span></a></p>

#Btrfs-progs 6.15 is out:

github.com/kdave/btrfs-progs/r

lore.kernel.org/all/2025062314

"'This is more of a bugfix release with a few feature updates.

Changelog:

* mkfs: new option --inode-flags to specify flags/attributes for inodes/directories/subvolumes
[…]
* rescue: add new command fix-data-checksum, selectively fix or find mismatching checksums
[…]"'

I have a bunch of old documents on my computer separated in an "old documents" folder. Currently they are not compressed.
If I compress my "old documents" into a tar.zst archive, will I increase to decrease the probability of them becoming corrupted?

My home partition is using BTRFS if it matters.
#BTRFS

"some performance improvements and one minor mount option update" are among the main #Btrfs changes merged for #Linux 6.16:

git.kernel.org/torvalds/c/5e82

A few highlights:

Performance:

- extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime)

- extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches

- more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%)

User visible changes:

- remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay'

- in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring)

Core:

- convert extent buffer radix tree to xarray

- continued preparations for large folios

git.kernel.orgMaking sure you're not a bot!

Linux 6.16 will see more btrfs improvements

The btrfs filesystem in Linux 6.16 has undergone many improvements that make its performance faster than before. It has already been improved across Linux releases, but the upcoming version of Linux sees even more improvements to this filesystem. Any system that uses this filesystem can now benefit from those improvements.

The buffer conversion work underwent some throughput and runtime improvements for metadata heavy operations, backed by several commits in a pull request made to the 6.16 branch, such as “extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime).”

The tree cleanups have been improved to avoid repeated or unnecessary searches. This improves the I/O performance, should any operation rely on tree cleanups. As for committing transactions, the extent unpinning action has become more efficient than before, yielding a 3-5% performance improvement in runtime.

You can find more about this pull request by clicking on the below button:

Learn more

Cover image credit.

The Great GitHub Nix Space Heist 🪓❄️

I've just released Nothing but Nix, a GitHub Action that transforms cramped 20GB GitHub runners into 130GB #Nix powerhouses! 💪

If you've ever hit thr no space left on device error when building #NixOS configs in CI, this one's for you.

This action:

  • Creates a large #BTRFS volume from free space on /mnt
  • Ruthlessly eliminates unnecessary packages in the background
  • Dynamically expands your Nix store as space becomes available

The results? All my large configurations (workstations and servers) now build successfully in CI 👍

Best of all, when I update systems, everything comes from my FlakeHub Cache with zero local compilation time ⚡Updates that used to require coffee breaks now happen in seconds! ⏱️

Check out the full technical details on my blog 👇

https://wimpysworld.com/posts/nothing-but-nix-github-actions/

Being both cheap and stubborn pays off sometimes 😉 #DevOps #GitHubActions