# btrfs Published articles for btrfs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## I moved my laptop to a rolling-release distro and the snapshots did the heavy lifting DevFeed: [I moved my laptop to a rolling-release distro and the snapshots did the heavy lifting]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-09-06T18:00:00Z Content type: opinion Language: en Sources: [Shed Stack]() Topics: [btrfs](), [Kernel](), [Hardware]() Tags: [boot](), [bootloader](), [btrfs](), [driver](), [laptop](), [packages](), [rollback](), [snapshots](), [update]() ### AI overview The author describes moving a laptop to CachyOS, a rolling-release distribution, to obtain newer kernels and packages. Automatic Btrfs snapshots managed with snapper provide rollback protection when updates affect boot components, drivers, or the desktop. ### Source excerpt CachyOS, snapper, and the DPTF fix. What a rolling release is actually like when you keep a parachute. ## BTRFS boot failure and easy GUI methods for system recovery DevFeed: [BTRFS boot failure and easy GUI methods for system recovery]() Original publisher: [Read original article]() Author: Alex Genovese Published: 2026-09-04T20:54:40Z Content type: article Language: en Sources: [Fedora Magazine]() Topics: [boot](), [Fedora](), [GUI](), [Linux](), [dnf](), [Software]() Tags: [backup](), [boot](), [btrfs](), [desktop](), [dnf](), [faqs-and-guides](), [fedora-project-community](), [for-system-administrators](), [gui](), [how-to](), [installation](), [iso](), [linux](), [recovery](), [snapshots](), [usb](), [using-hardware](), [using-software](), [workstation]() ### AI overview This how-to article explains GUI-based recovery options for Fedora Linux systems using BTRFS. It covers booting from a USB live ISO, checking whether the operating system uses BTRFS, and recovering earlier system states with snapshot tools such as btrfs-assistant and snapper. ### Source excerpt A few short how-to's with screenshots, showing easy ways to boot up off a USB live ISO and return back to previous points in time with BTRFS ## Linux swap Commands: Create and Manage Swap Files/Partitions DevFeed: [Linux swap Commands: Create and Manage Swap Files/Partitions]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-08-26T15:13:53Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [btrfs](), [Kernel](), [rhel]() Tags: [blog](), [btrfs](), [commands](), [desktop](), [files](), [fstab](), [gotchas](), [guide](), [how-to](), [linux](), [partition](), [performance](), [server](), [sysadmins]() ### AI overview A practical guide to creating, activating, deactivating, and troubleshooting Linux swap files and partitions using mkswap, swapon, and swapoff. It also explains filesystem-specific considerations, including Btrfs and older XFS kernels. ### Source excerpt A practical guide to creating, managing, and tuning swap files and swap partitions on Linux using mkswap, swapon, and swapoff, with real commands and common troubleshooting fixes. Continue reading... ## Testing crash recovery features in a CI environment DevFeed: [Testing crash recovery features in a CI environment]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2025-09-09T00:05:00Z Content type: article Language: en Sources: [Andrea Corbellini]() Topics: [Filesystems](), [btrfs](), [Linux](), [Rust]() Tags: [atomic](), [btrfs](), [filesystem](), [information-technology](), [linux](), [rust]() ### AI overview A technical article describes atomic file updates in a Rust crate, using temporary files, synchronization, and atomic renaming to ensure a file contains either its old or new contents after a crash. It also discusses Linux anonymous temporary files and their limitations, including filesystem support and btrfs. ### Source excerpt About two years ago I wrote a Rust crate to fulfill this promise: If a crash occurs while updating a file, the file either contains the old contents, or the new contents, nothing in between. This crate essentially solves the following problem: when you update a file, generally you open it, truncate it, write to it block-by-block, and eventually close it. The problem with ... ## Easy Automated Docker Volume Backups That Are Database Friendly DevFeed: [Easy Automated Docker Volume Backups That Are Database Friendly]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2025-05-10T12:00:00Z Content type: tutorial Language: en Sources: [Nic Raboy]() Topics: [Docker](), [Docker Compose](), [Filesystems](), [SQLite](), [btrfs](), [Ubuntu]() Tags: [backrest](), [btrfs](), [compose](), [docker](), [filesystem](), [nas](), [offen](), [restic](), [sqlite](), [synology](), [ubuntu-server](), [volume]() ### AI overview A tutorial on automated, database-friendly backups for Docker volumes on Ubuntu Server with ext4. It explains the risk of corruption when files, especially SQLite databases using WAL, are active during backup, and introduces Offen and Backrest as automated solutions. ### Source excerpt I recently picked up a Beelink EQR6 Mini PC to reduce some of the Docker stress on my aging Synology NAS. Since my Synology used the Btrfs filesystem, I never had to worry about file locks and corrupt... The post Easy Automated Docker Volume Backups That Are Database Friendly appeared first on The Polyglot Developer. ## May and June 2021 round-up DevFeed: [May and June 2021 round-up]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2021-07-06T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Mobile](), [Nix](), [btrfs](), [boot](), [Arm]() Tags: [boot](), [btrfs](), [crash](), [devices](), [pull-requests](), [recovery](), [series](), [update]() ### AI overview The May and June 2021 Mobile NixOS project update reports merged changes, ongoing Plasma Mobile and Nixpkgs work, recovery and boot menu improvements, a tracked reproducible crash, BTRFS support for custom images, camera enablement on Pinephone, and support for three additional devices. ### Source excerpt This update is the seventeenth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes During the two months 10 pull requests were merged. Not too different from last update, work has happened, but not present as merged pull requests in the Mobile NixOS repository. In addition, some time was spent by the main author working on a side-project, unrelated to Mobile NixOS, but related to NixOS on ARM. Fear not, work is not really expected to slow down. What's been done elsewhere Let's not forget the still in-progress Plasma Mobile work. The initial pull request now includes only Plasma Mobile itself, while a new pull request was opened for the Plasma Mobile applications (#125156). Doing so should make it easier to finish up and land the changes, as it's simply too big otherwise. Work upstream on Nixpkgs has been started to refresh the Anbox module (#125600). Preview of what's coming While a more in-depth write-up will come with the next update, pull request #364 refreshes the recovery and boot menu appearance. While working on this refresh, time was spent tracking down a rare, but reproducible crash. Notable changes Allow using specialArgs for use with Nix flakes (#354) [@Pacman99] When building custom images, BTRFS can be used for the filesystem (#256) [@lheckemann] Device-specific changes Pinephone improvements Enable camera (#355) [@zhaofengli] (See also Nixpkgs#121722) Ports Support for three new devices was merged in this period. Amazon Fire 7 (7th generation) (2017) [@samueldr] (#311) Motorola Moto G5 Plus [@telent] (#359) motorola moto g(8) [@samueldr] (#369) Bringing the total of devices to 21. ## Victor Perevertkin hired full-time to work on the storage stack DevFeed: [Victor Perevertkin hired full-time to work on the storage stack]() Original publisher: [Read original article]() Published: 2020-07-14T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [toolchain](), [USB](), [btrfs](), [Compiler](), [upgrade]() Tags: [btrfs](), [compiler](), [free](), [kernel](), [open-source](), [os](), [react](), [reactos](), [toolchain](), [upgrade](), [usb](), [win32](), [winapi]() ### AI overview ReactOS Deutschland e.V. hired Victor Perevertkin full-time for three months to work primarily on the ReactOS storage stack. Planned work includes making scsiport Plug & Play aware, fixing kernel Plug & Play bugs, and improving USB storage support and compatibility with Windows storage drivers. ### Source excerpt I am proud to announce that ReactOS Deutschland e.V. has hired Victor Perevertkin to work full-time on the ReactOS storage stack for the next 3 months. Victor has been a proven contributor to various ReactOS components since 2018. He already got deep into the kernel side of things when writing Btrfs boot sector code in his GSoC debut, later managed the integration of a new USB stack, and recently touched nearly all parts of ReactOS when preparing it for the major upgrade to a new compiler toolchain. ## ReactOS 0.4.11 released DevFeed: [ReactOS 0.4.11 released]() Original publisher: [Read original article]() Published: 2019-03-04T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [version](), [Filesystems](), [btrfs]() Tags: [btrfs](), [filesystems](), [free](), [kernel](), [memory-leak](), [open-source](), [os](), [processors](), [react](), [reactos](), [release](), [version](), [win32](), [winapi]() ### AI overview The ReactOS team announces version 0.4.11, describing kernel, storage, filesystem, and application-loading changes intended to improve system stability and compatibility. The release includes fixes for a cache-controller issue, BTRFS memory leaks, Skylake AHCI incompatibility, and manifest support. ### Source excerpt The ReactOS team is pleased to announce the release of version 0.4.11. This version has seen substantial work done to the kernel, helping improve overall system stability. Kernel Improvements While the term kernel is used as a sort of catch-all term, in truth the range of functionality that it encapsulates is quite wide. One case in point is the kernel's responsibility for managing file I/O. A mistake here can cause subtle data corruption to more obvious hard crashes. ## ReactOS 0.4.10 released DevFeed: [ReactOS 0.4.10 released]() Original publisher: [Read original article]() Published: 2018-11-06T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [releases](), [btrfs](), [version](), [boot](), [Front end]() Tags: [boot](), [btrfs](), [consistency](), [free](), [frontend](), [improvements](), [new-features](), [open-source](), [os](), [react](), [reactos](), [release](), [releases](), [version](), [win32](), [winapi]() ### AI overview The ReactOS project released version 0.4.10 as part of its quarterly release cadence, emphasizing consistency, stability, and end-user experience. The release adds the ability to boot ReactOS from BTRFS-formatted drives and includes frontend improvements. ### Source excerpt The ReactOS project is pleased to announce the release of version 0.4.10, the latest of our quarterly cadence of releases. The project has seen an increasing emphasis on consistency and stability over the past few months, an emphasis the rapid release schedule helps reinforce to provide a better end-user experience. Even as new pieces of functionality are added, all this would be for naught if a user could not access them reliably. ## GSoC 2018 - Final report DevFeed: [GSoC 2018 - Final report]() Original publisher: [Read original article]() Published: 2018-08-17T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [btrfs](), [systems](), [boot]() Tags: [boot](), [btrfs](), [free](), [gsoc](), [implementation](), [memory-leak](), [open-source](), [operating-systems](), [os](), [react](), [reactos](), [report](), [win32](), [winapi]() ### AI overview This final report describes a Google Summer of Code project to add missing ReactOS support for booting from BTRFS. It covers read-only BTRFS support in FreeLoader, BTRFS partition formatting and installation, driver and ReactOS bug fixes, and a remaining memory leak that prevented ReactOS self-hosting on BTRFS. ### Source excerpt Introduction WinBtrfs is a feature-complete IFSD (Installable File System Driver) for NT operating systems, written by Mark Harmstone. This driver is checked into the ReactOS source code for some time already. My main goal for this GSoC project was to implement all missing features (and fix bugs, of course) in ReactOS that prevents booting from BTRFS file system. Links All work is merged into gsoc2018_all branch in my ReactOS fork on GitHub. ## July 2018 meeting minutes DevFeed: [July 2018 meeting minutes]() Original publisher: [Read original article]() Published: 2018-08-16T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Git](), [Submodules](), [btrfs](), [pull-requests]() Tags: [also](), [btrfs](), [free](), [git](), [open-source](), [os](), [react](), [reactos](), [reports](), [submodules](), [win32](), [winapi]() ### AI overview The ReactOS July 2018 meeting covered contributor status reports, the upcoming Hackfest, plans to split ReactOS components into Git submodules, and the project's 20th anniversary. Contributors also reported work on the 0.4.9 release, testing, web services, system information, WinBtrfs, and related bug fixes. ### Source excerpt 2018-08-02 19:00 UTC #meeting Proceedings Meeting started at 19:01 by Colin Finck. Point 1: Status Reports Point 2: Upcoming Hackfest Point 3: Splitting off ReactOS components into Git submodules Point 4: Celebrating 20 years of ReactOS Point 1: Status Reports Alexander Rechitskiy did some PR work for ReactOS and spread info about recent developments and the 0.4.9 release. Aleksandar Andrejevic mentioned he is thinking about continuing his audio work. ## GSoC 2018 - booting from BTRFS works! DevFeed: [GSoC 2018 - booting from BTRFS works!]() Original publisher: [Read original article]() Published: 2018-07-29T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [btrfs](), [ReactOS](), [Filesystems](), [bug](), [Windows](), [Oracle-VM-VirtualBox]() Tags: [btrfs](), [bug](), [free](), [git](), [gsoc](), [issue](), [open-source](), [os](), [pull-request](), [react](), [reactos](), [virtualbox](), [win32](), [winapi](), [windows]() ### AI overview This progress report describes ReactOS booting from a BTRFS partition. Freeloader can read files and follow symlinks, and fixes were made for a VirtualBox BIOS limitation and a WinBtrfs driver bug. The system can boot to the desktop in a relatively stable state, but pagefile creation, some write operations, and shutdown stability remain unresolved. ### Source excerpt Hi, all! Here is what happened since last post: Freeloader is now able to read files and follow symlinks from btrfs partition. One major issue is left here - case sensitivity. BTRFS is case-sensitive file system, so paths like /ReactOS/System32, /reactos/system32, /ReactOS/system32 are different here. But in Windows world most software is written assuming that case does not matter during path lookup. This thing is solved in WinBtrfs driver, but for Freeloader it can be a bit tricky. ## June 2018 meeting minutes DevFeed: [June 2018 meeting minutes]() Original publisher: [Read original article]() Published: 2018-07-22T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Development](), [migration](), [Authentication](), [WINE](), [btrfs](), [Git]() Tags: [btrfs](), [development](), [free](), [git](), [migration](), [minutes](), [open-source](), [os](), [react](), [reactos](), [reports](), [win32](), [winapi](), [wine]() ### AI overview ReactOS's June 28, 2018 meeting covered developer status reports, preparations for the August Hackfest, uncertainty about the planned 0.4.9 release date, and recruitment for a website developer or maintainer. Developers also discussed RosLogin authentication modules, a migration script, Wine-related work, Git Bash compatibility, and BTRFS bootsector code. ### Source excerpt 2018-06-28 19:00 UTC #meeting Proceedings Meeting started at 19:04 by Mark Jansen, as Colin Finck was running late. Point 1: Status Reports Point 2: ReactOS Hackfest on August 16-21 Point 3: 0.4.9 release on July 14 Point 4: Website developer/maintainer Point 1: Status Reports Amine Khaldi is doing the usual, Wine syncs and anything he can help with. Colin Finck has been working on authentication modules for RosLogin and the final migration script. ## GSoC 2018 - boot sector finished DevFeed: [GSoC 2018 - boot sector finished]() Original publisher: [Read original article]() Published: 2018-07-10T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [btrfs](), [boot](), [Filesystems](), [x86](), [Emulator](), [Development](), [Refactoring](), [Testing]() Tags: [boot](), [bootloader](), [btrfs](), [emulator](), [filesystems](), [free](), [gsoc](), [open-source](), [os](), [react](), [reactos](), [refactoring](), [testing](), [time](), [win32](), [winapi](), [x86]() ### AI overview A GSoC 2018 progress update reports that the ReactOS BTRFS boot-sector code can load freeldr.sys into memory and transfer control to it. The work still needs refactoring and testing on larger filesystems, while second-stage BTRFS support in freeldr.sys is in progress. ### Source excerpt Hi all! Sorry, haven't written anything for a while. Let me tell you what have been done since last post. BTRFS boot sector TL;DR: It works! I've been able to load main bootloader code from freeldr.sys into memory, transfer control to it and get on error message (freeldr.sys can't find its config file - I haven't written second-stage BTRFS code yet). It was not that easy because we are in x86 real mode when running boot sector thus only about 1mb of memory is available. ## GSoC 2018 weeks 3-4 - understanding BTRFS internals DevFeed: [GSoC 2018 weeks 3-4 - understanding BTRFS internals]() Original publisher: [Read original article]() Published: 2018-06-14T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [btrfs](), [Python](), [virtualbox image]() Tags: [btrfs](), [free](), [open-source](), [os](), [python](), [react](), [reactos](), [virtualbox-image](), [win32](), [winapi]() ### AI overview A GSoC progress post describing work to understand Btrfs on-disk structures. The author wrote a Python parser for basic Btrfs structures, item types, B-tree searches, and logical-to-physical address translation, then used it to read freeldr.sys from a filesystem blob. ### Source excerpt Hi all! This two weeks I was diving into btrfs structures and on-disk layout. Writing an ASM program from scratch is not that simple so I decided to convert a VirtualBox image with BTRFS filesystem in it to raw file and write a python script to parse and show internal filesystem structures. It was also useful for understanding how files are stored in FS, because information on btrfs.wiki.kernel.org was not enough for me to understand some corner cases. ## GSoC 2018 - Project BTRFS Boot DevFeed: [GSoC 2018 - Project BTRFS Boot]() Original publisher: [Read original article]() Published: 2018-05-29T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [btrfs](), [ReactOS](), [boot](), [debugging](), [Kernel](), [Assembly]() Tags: [assembler](), [bootloader](), [btrfs](), [bugs](), [debugging](), [free](), [gsoc](), [open-source](), [os](), [project](), [react](), [reactos](), [win32](), [winapi]() ### AI overview A ReactOS GSoC 2018 progress report describes work to add installation and boot support for BTRFS partitions. During the first two weeks, the author explored setup utility internals, enabled BTRFS formatting and installation, and tested the FreeLdr bootloader with Windows XP and Windows 2003, which still had some bugs. ### Source excerpt Introduction Hi all! My name is Victor Perevertkin and I am the only GSoC student in ReactOS project this year :) This is my first GSoC and I was very excited when I realized that I was selected and there will be four mentors for me. I will definitely learn a lot from this internship! My project is both simple and complicated. I want to add to ReactOS an option to install on and boot from BTRFS partitions. ## ReactOS 0.4.1 Released DevFeed: [ReactOS 0.4.1 Released]() Original publisher: [Read original article]() Published: 2016-05-17T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [releases](), [version](), [btrfs](), [Oracle-VM-VirtualBox](), [virtual machines]() Tags: [btrfs](), [free](), [new-features](), [open-source](), [os](), [react](), [reactos](), [release](), [usability](), [usb](), [version](), [virtual](), [virtual-machines](), [virtualbox](), [vmware](), [win32](), [winapi]() ### AI overview The ReactOS team announced version 0.4.1, released three months after version 0.4.0. The release refines the previous version and adds or improves activation context handling, BTRFS support, shell usability, USB stability, virtual machine shared folders, and drive support. ### Source excerpt The ReactOS team is proud to announce the release of version 0.4.1 a mere three months after the release of 0.4.0. The team has long desired an increased release tempo and the hope is that this will be the first of many of faster iterations. Due to the brief period of time between the two releases, 0.4.1 is ultimately a refinement of what was in 0.4.0. That is not to say that there are no new features of course, and a few highlights of both categories are listed below. ## A Practical Comparison of Docker Graphdrivers DevFeed: [A Practical Comparison of Docker Graphdrivers]() Original publisher: [Read original article]() Published: 2016-04-02T18:47:47Z Content type: opinion Language: en Sources: [Jessie Frazelle]() Topics: [Docker](), [Kernel](), [btrfs](), [Ubuntu](), [Debian]() Tags: [btrfs](), [debian](), [docker](), [kernel](), [opinion](), [ubuntu]() ### AI overview The article gives an opinionated comparison of Docker graphdrivers, discussing Overlay, Aufs, Btrfs, Zfs, Devicemapper, and Vfs. It highlights kernel requirements, setup complexity, distribution support, and reported issues for each driver. ### Source excerpt Sup, let me give you fair warning here. Everything contained in this post is my opinion so don't go getting your panties all in a knot on Hacker News because you don't agree with me. I could honestly care less, because that's the thing about my opinion, it's mine. I am going to give you my honest and dare I say it "blunt" opinion about each of the Docker graphdrivers so you can decide for yourself which one is the best one for you. None are perfect each has it's flaws and I will be laying those out. Let's begin. Overlay Overlayfs was added in the 3.18 kernel. This is important to note because if you are running overlay on an older kernel than 3.18 you are either: Not running the same overlay. Running a kernel with overlayfs backported onto it, which is what we call a "frankenkernel". Frankenkernels are not to be trusted. This is not to say it won't work, hey it might work great, but it's not to be trusted. Overlay is great but you need a recent kernel. There are also some super obscure kernel bugs with regard to sockets or certain python packages docker/docker#12080. But I will say personally I use overlay, I have not hit these bugs recently and I have all my 100+ dockerfiles running as continuous builds on my server with overlay and they all work. Aufs Aufs is another great one. But it is not in the kernel by default which blows. On Ubuntu/Debian distros this is as easy as installing the kernel extras package but other distros it might not be as simple. Btrfs Btrfs is great too but you need to partition the disk you will use for /var/lib/docker as btrfs first. This is kinda a hurdle to jump that I don't think a lot of people are willing to do. Zfs Zfs is another good one, of course, like btrfs it takes some setup and installing the zfs.ko on your system. But this driver might become a whole lot more popular if Ubuntu 16.04 ships with zfs support. Devicemapper Honestly it makes me super disappointed to say this, but buyer beware. Hey on the plus side.... it's in the k ## OS X + ZFS DevFeed: [OS X + ZFS]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-02-21T19:28:00Z Content type: opinion Language: en Sources: [Keith Smiley]() Topics: [Filesystems](), [btrfs](), [Open Source](), [WebKit](), [Google Chrome]() Tags: [btrfs](), [filesystem](), [google](), [google-chrome](), [open-source](), [opinion]() ### AI overview The article argues that Apple should replace HFS+ with a modern, openly available filesystem. It recommends adopting BTRFS or an open ZFS port, following the model of WebKit, to encourage broader vendor compatibility, development, and stability. ### Source excerpt For a long time people have talked about how horrible HFS+ is. Most notably, in my opinion, Linus Torvalds (the creator of Linux and Git) who said "Their file system is complete and utter crap, which is scary." John Siracusa also wrote about the problems with HFS+ in his 10.7 review along with talking about it on his podcast, Hypercritical in episodes 56 and 57. The gist of all this really is that Apple needs a new filesystem. It has been a while since Apple had ZFS support on their website for release in Snow Leopard. After which Apple dropped ZFS support because of licensing issues. There had been talks of Apple developing their own file system, although I think that's the wrong way to go. I think Apple needs to approach file systems the way they approached Safari with Webkit. I think they would be best served by picking up a liberally open source file system, such as BTRFS, or grabbing up one of the ZFS ports and continuing development while leaving it open for anyone to use. One of the great things about this approach is exactly what happened with Webkit and Google Chrome. Google decided to use the Webkit engine to make a product that competes with the main developers of the Webkit project. By doing this with a file system other vendors could use the same implementation and therefore increase development and in turn stability of whichever system was chosen (not to mention compatibility). One thing is for sure. People who understand how integral a file system is want something modern.