/en/tags/btrfs/Recent content in Btrfs on Xerxes II's BlogHugoenMon, 06 Apr 2026 00:00:00 +0000/en/posts/optimize-rust-compile-time-space/Mon, 06 Apr 2026 00:00:00 +0000/en/posts/optimize-rust-compile-time-space/<p>Slow compilation and massive <code>target/</code> directories — the classic Rust complaints. This post documents the techniques I&rsquo;m currently using to make things better, using my project <a href="https://github.com/Xerxes-2/clewdr">ClewdR</a> (an async web service with 394 crate dependencies) as an example.</p> <p>Environment: Rust 1.94.1, CachyOS (Arch-based), NVMe SSD, Btrfs.</p> <h2 id="rust-lld">rust-lld</h2> <p>Linking is the final step of Rust compilation, and traditionally the slowest. GNU ld performs terribly here, especially with LTO enabled.</p> <p>The old approach was to manually install <code>lld</code> or <code>mold</code> and configure <code>.cargo/config.toml</code>:</p>/en/posts/ext4-to-btrfs-oracle-cloud/Mon, 06 Apr 2026 00:00:00 +0000/en/posts/ext4-to-btrfs-oracle-cloud/<p>A writeup of converting an Oracle Cloud Ubuntu 26.04 ARM VM from ext4 to Btrfs in place.</p> <blockquote> <p><strong><span style="color:red">WARNING</span>: The operations in this post involve an in-place filesystem conversion — if anything goes wrong, data cannot be recovered. My VM was a blank machine with no important data, which is the only reason I felt comfortable doing this. If your machine has anything you can&rsquo;t afford to lose, make sure you have a full backup first (Oracle Cloud Boot Volume Backup, rsync to a remote, dd image, etc.), and verify it&rsquo;s actually restorable before proceeding. A failed filesystem conversion with no backup means total data loss — there&rsquo;s no undoing it.</strong></p>