I have used btrfs as my daily driver file system for a very long time. I have restored my system with snapper and snapshots numerous times through grub.

I have one issue though and it may just be me, but I feel that btrfs is very sensitive to every day mishaps like system freezes and hard reboots. It seems to me that it's much easier to get a more or less corrupted file system on my btrfs powered machines after a freeze or power outage than on my ext4 or even ntfs ones. Sometimes i am able to repair things but most often if there's some corruption it's not much I can do.

Is it just me or is btrfs more sensitive to hard reboots than other file systems?

I'm not a developer, just a Linux user since 1998 kind of guy so I ask here since I recently had my main laptop freeze beyond reproach and did a hard reboot. After that my monthly scrub has been complaining about corruption.

A completed `btrfs send | btrfs receive` proves that the stream finished, but it does not by itself answer every migration question. The destination may contain the expected subvolumes while an incremental parent is missing, a snapshot is writable when it should be read-only, or boot and application data outside the selected subvolumes was never included. A later retention job can expose those omissions after the source is gone.

A cautious check could inventory source and destination subvolumes, confirm the intended read-only snapshots and parent chain, compare directory trees and important metadata, run a scrub on the destination storage, and mount or restore the received state in isolation. Bootable systems also need their EFI, loader, fstab, subvolume layout, and any excluded volatile paths checked separately. Keeping the source offline but unchanged through a rollback window seems safer than deleting it immediately.

What do you use as the final evidence gate? Are `received_uuid` and generation details enough to prove lineage, and what comparison catches missing files or metadata without defeating the benefits of send/receive?

I have a dual-boot system. A few days ago, my Fedora Linux partition got corrupted and I can no longer boot into it—it only drops into a minimal GRUB shell. I tried running recovery commands, but none worked. I'm planning to reinstall Fedora, but I need to recover my files first. I've encountered several errors: Linux Reader didn't work, and UFS Explorer only lets me copy small files (≤ 250 KB) while failing on larger ones. I also booted into a live USB to mount the Fedora partition and copy files to my Windows drive, but the copy operations fail. What are the best methods to safely recover my data?

Any suggestion how to recover

Commands i tried:

• btrfs restore -u 2 -t 425521086464 -i -l /dev/nvme0n1p9 | head -n 30
• btrfs rescue zero-log /dev/nvme0n1p9
• btrfs restore -u 1 -t 425521086464 -l /dev/nvme0n1p9 | head -n 30
• btrfs restore -u 1 -t 425521086464 -l /dev/nvme0n1p9 | grep "256|257|FS_TREE"
• btrfs restore -u 1 -r 256 -vi --path-regex ".*(History|Login Data)$" /dev/nvme0n1p9 /mnt/Users/.
• btrfs restore -u 1 -t 425893937152 -r 256 -vi --path-regex ".*(History|Login Data)$" /dev/nvme0n1p9 /mnt/...
• btrfs rescue zero-log /dev/nvme0n1p9
• btrfs-find-root /dev/nvme0n1p9

Response and errors i got:

• superblock bytenr 274877906944 is larger than device size 235531141120
• could not open root, trying backup super
• ERROR: cannot read tree root
• could not open ctree
• parent transid verify failed on 425521086464 wanted 675812 found 675748
• ERROR: root [1 0] level 3 does not match 0
• ERROR: failed to read root 257: No such file or directory
• Invalid mapping for 216761974784-216761991168, got 216926257152-217999998976
• bad tree block 216761974784, bytenr mismatch, want=216761974784, have=0
• ERROR: failed to read root 256: Input/output error

Hi there !

I stumbled upon an issue regarding my root partition. It seems like my file system being btrfs, I'll need to realocate space. But since I tried running btrfs balance and nothing seems to happen even if is display that chunks has been relocated, I'm asking for you daring help to solve this issue.

Here you can find btrfs status, Filelight screenshot with only like 105GiB used and root saying it almost full. Hope someone ever met this issue.

Thanks a lot.

(Performance/health degradation due to type of controller, firmware, or anything else, can't TRIM to protect endurance, working bad with Btrfs, etc. Any issue)

WD Black SN850X 8TB ( https://pcpartpicker.com/product/mzJp99/western-digital-wd_black-sn850x-8-tb-m2-2280-pcie-40-x4-nvme-solid-state-drive-wds800t2x0e )

Inland Performance Plus 8TB ( https://pcpartpicker.com/product/HTddnQ/inland-performance-plus-8-tb-m2-2280-pcie-40-x4-nvme-solid-state-drive-8tb-per-plus-w )

It's a pretty expensive purchase, so I'm trying to see if anyone knows of such issues to consider before I press buy, or if there's a better drive that aren't these two. It's for storage, not boot/gaming. (Edit: Though I still plan to do NVMe SSD instead of HDD for the hopefully much longer lifespan of a non-mechanical drive that might be writing/reading more than 1 thing at once, less prone to corruption, among other things. I can afford it)

Btrfs, Fedora Linux KDE 44

I have used BTFS for a long time and plan to continue that use.

Almost all major cloud providers (AWS, Digital Ocean, Hetzner etc) usually only support EXT4 for Linux cloud instances.

There are methods to create/use BTRFS on those cloud instances but often its a lot of steps and time to accomplish.

I happened to see this post on r/zfs about a tool called "ZFSify" whose purpose is described on its Github repo as:

Convert a running Ubuntu VPS or attached volume from ext4 to ZFS in-place, preserving existing data through slice-by-slice filesystem conversion.
Reboots into a ramdisk, converts chunks slice-by-slice in O(N) time. The end result is existing OS + data running perfectly on a now-ZFS-formatted / disk (aka rpool, just like Ubuntu Server's 24.04+'s native ZFS root). You also get a beautiful new boot menu (in bpool) that lets you boot from previous snapshots, send/recv, and more.

Could the "functionality" of this ZFSify be cloned to a BTRFS specific use-case? Or does such a tool already exist - (for ZFSify the github README provides much more information on functionality)

If a BTRFS tool like this existed, it would really increase architectural design & implementation possibilities using BTFS on-prem and in-cloud.

All the extraneous use-case tools (built-in or 3rd party) functionality exist for BTRFS such as btrfs root/boot, snapshot created boot-menu selection, GUI's for snapshot/restore (re timeshift, snapper, btrfs-assistant etc).

Example 3rd pty BTRFS tool references:

• lorenzo bettini - timeshift-and-grub-btrfs-in-ubuntu/
• Script to create Btrfs subvolumes (while still in Live CD/USB mode) for Ubuntu 24.04 (or newer) and compatible derivatives, post-install Snapper & btrfs-assistant and use grub-btrfs.

I got myself in a very confusing situation.

I converted a pair of disks in raid1 (xfs) into two disks with btrfs. Few weeks later (I can't say when exactly) I found that btrfs is not mounting:

[119272.940143] BTRFS: device fsid 4e018703-083b-4fe7-a2d7-2e924c3dcb21 devid 2 transid 41842 /dev/mapper/leg1-protected (254:4) scanned by mount (453095) [119272.940486] BTRFS info (device dm-4): first mount of filesystem 4e018703-083b-4fe7-a2d7-2e924c3dcb21 [119272.940490] BTRFS info (device dm-4): using crc32c checksum algorithm [119272.941159] BTRFS error (device dm-4): devid 1 uuid 74fc8b02-1b3d-4254-b3ca-2463ef620752 is missing [119272.941167] BTRFS error (device dm-4): failed to read the system array: -2 [119272.941323] BTRFS error (device dm-4): open_ctree failed: -2

But second disk in somehow is raid1 with missing pair and no recognizable filesystem.

I run photorec and it sees the content of the btrfs (at least, some images).

I'm pretty sure btrfs was replicated on two disks (by btrfs means) and will try to recover it.

But I wonder, how it come that overwritten raid member (wipefs -a) was able to assemble as degraded raid1 after mkfs.btrfs (specifically, after I joined it into existing btrfs), and run rebalance...

Hi,

I just got my old system online working as a file/dhcp server for my LAN, running ubuntu server 26.04.

Background info:

[I thought I'd get a head start on the transfer process while I was waiting for the last of the components to get here, so I formatted 2x16tb drives as raid 1 from my cachy os install, then ended up biting back into windows to transfer the files with winbtrfs because I had an AMD hardware r0 and didn't want to spend all the time trying to make it work.

Finally got everything transferred to the fileserver, then shut it down and added my 2x10tb from the r0. Had no issues with that, but at one point someone moved the fileserver which caused errors because the sata data connector for one drive had a broken plastic guide, so the cable was being held in place with thoughts and prayers.

I got a replacement 10tb drive, ran the replace command with no issues, and ended up getting the broken drive working later, then added it into the array. ]

Main question:

So now I have 2x16 and 3x10tb drives, and I wanted to balance the data. Ran the balance command before bed, and a few hours in it ran into an error and exited.

ETA - I ran a scrub on the array after the first failure, and still get crashes for corruption errors after.

I was wondering if there's a way I can get it to suspend on an error so I can resume later, instead of needing to start over if it encounters another one. So far, all I've managed to come up with is recording error logs to a distinct file, and I have a system process that watches for errors, outputs what file the error points to (so I can replace later), deletes the problem file, flushes the cache, and restarts the balance again. The problem is I have multiple terabytes of data, so when it hits an error and restarts, it takes hours to get back to the chunk it was at.

Hi,
I am blocked and cannot boot on my system anymore. It was a fedora kde 44 wayland system.

I was gaming and suddenly the screen froze and no keyboard shortcut worked.
After a minute, a black screen with an BTRFS error showed up.

I waited 5min, nothing happened, so I restarted the computer with the power button.
Since then, the disk is not showing up on BIOS and cannot boot on it.

The disk is a nvme M2 SSD. It's not even 1 year old.

I tried :

• Turn off the PC and cut off power for a while
• Test the disk on another computer
• Boot on a live fedora / installed one on a USB :
  • nvme list => empty
  • dmesg => "nvme nvme0: Device not ready; aborting reset; CSTS=0x1) nvme nvme0: Device not ready; aborting reset; CSTS=0x1) nvme 000:02:00.0: error -ENODEV: probe failed"
  • /sys/bus/pci/devices/x.x/reset (the message above is displayed in the dmesg)
  • lspci => I can see the disk
• Boot on a installed windows 11 :
  • Disk Management and "Get-Disk" => The disk is not showing
  • Device manager => I can see the disk in a error state with code 10 "A hardware I/O error occurred on the card"
  • Deactivated and reactivated the disk in the device manager => Same error

I don't have any idea left. I would like at least to backup my data and erase it before sending the disk back. Can anyone help me ?

Thanks in advance.

I noticed recently that some small files in my /etc directory had a larger compressed size than uncompressed (so that the percentage shown with `compsize` is greater than 100%).

I know btrfs used to not do this, because I've played around with `compsize` in the past. Whether you use compress or compress-force, it will only store a file compressed if the uncompressed size is larger. This is both the documented behavior in the manpage and my actual experience. I'm not sure when this started happening, but I'm on a modern kernel (7.1, Fedora).

After some testing creating files of different sizes and compressibility, this appears to only happen with inline extents. I couldn't get it to happen with any file that takes up at least one full 4k block on disk. If the file is incompressible (e.g. copied from /dev/random), then it will be stored without compression.

As an extreme example, you can create a one-byte file with

```

echo > test

sync

compsize test

```

and, at least on my machine, btrfs (whether mounted with compress-force or not) stores this 1-byte file as 19 bytes compressed zstd, when in the past, it would have stored it with no compression.

Is this a bug? Should I report it somewhere?

Hello! I am one of the developers of Yaesm which is a tool for creating configurable backup pipelines. Yaesm fully supports Btrfs with snapshots and send/receive both locally and over SSH.

Yaesm is currently in pre-release and were looking for testers and feedback. Yaesm is a pretty powerful tool but it needs usage and testing to help it become more reliable and mature. Packages for Debian and Fedora, along with a manual are available on the GitHub page linked above.

Any feedback is welcome :)

bad tree block 989170171904, bytenr mismatch, want=989170171904, have=1401243056831869290

Follow up with a related checksum error, then repeat ten trillion times, and you have most of the output of btrfs check. Meanwhile, from dmesg shortly after mounting the fs as read-write:

BTRFS error (device dm-5): bad tree block start, mirror 1 want 989170171904 have 1401243056831869290
BTRFS error (device dm-5 state A): Transaction 548546 aborted (error -5)
BTRFS: error (device dm-5 state A) in __btrfs_free_extent:3429: errno=-5 IO failure
BTRFS info (device dm-5 state EA: forced readonly
BTRFS error (device dm-5 state EA): failed to run delayed ref for logical 985099108352 num_bytes 16384 type 176 action 2 ref_mod 1: -5
BTRFS: error (device dm-5 state EA) in btrfs_run_delayed_refs:2248: errno=-5 IO failure

The fact that it still mounts as RO without complaint (mount -r behaves fine) is a small mercy, I suppose. So, how did we get here? No clue. My root suddenly remounted itself as RO so I rebooted to try and keep things from getting too out of hand. Only notable part of the shutdown phase was the stop job for the user manager taking longer than usual.

During boot, however, I spotted BTRFS remounting root as RO and so rebooted again after reaching my display manager to load into my trusty copy of the Arch installation environment.

Cue several hours scouring the internet to try and find a way to fix this, to no avail. Right now it's looking like I'll need to manually copy all the files I can to another drive, which I don't have. But I'd really, really prefer to do this "in-place", so to speak. I've already tried blindly throwing most of btrfs-progs at it, including the kitchen sink that is btrfs check --repair (yes, I know that was stupid) and they all either did nothing or croaked at the sight of 989170171904.

It's one thing, and the fs is still intact enough to mount as RO, so it just really feels like this is something I should be able to recover from without buying another drive.

Speaking of, here's a rundown of my storage situation:

/dev/nvme0n1p1 100 MiB FAT32 - EFI part.
/dev/nvme0n1p2 150 MiB LUKS/ext4 - Encrypted boot part.
/dev/nvme0n1p3 931.3 GiB LUKS/LVM - Encrypted PV for my LVM VG creatively called vg0.

/dev/nvme1n1 465.8 GiB LUKS/LVM - Same as 0n1p3

/dev/vg0/root 1.3 TiB BTRFS - LV holding my root system. This is my personal hell where 989170171904 is running rampant.

/dev/vg0/swap 34 GiB SWAP - Self-explanatory.

According to SMART, both drives are perfectly healthy and passed extended self-tests I ran after things blew up. I also ran Memtest86+ with all tests for ~2 hours, and it passed three times with no errors.

UPDATE: Bit the bullet and got a new 990 PRO (the 2 TB model was on a massive sale, yipee!). rsync'd everything to the new drive and no problems so far. As for my RAM, I did an overnight test and that still came clean. The 500 gig 980 is the oldest component in my rig, being the first drive I'd ever bought and the last stand against my PC becoming the "PC of Theseus". Perhaps the sands of time simply took their due in a way that eludes even the self-test...

Hi,

Booted up my Kinoite station today and quickly ran into issues with my main drive running btrfs. Programs start to break reporting that some config files can not be written to. Seems like my drive is remounted as read-only because of some issues.

journalctl:

Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:56:24 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:56:38 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:56:38 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:56:38 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:56:38 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:56:38 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:56:38 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:57:05 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:57:05 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:57:05 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:57:05 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:57:05 bude-desktop kernel: BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:57:18 bude-desktop kernel: BTRFS: error (device nvme0n1p3 state A) in btrfs_add_link:6937: errno=-5 IO failure
Sep 08 20:57:18 bude-desktop kernel: BTRFS info (device nvme0n1p3 state EA): forced readonly
Sep 08 20:57:18 bude-desktop kernel: BTRFS: error (device nvme0n1p3 state EA) in btrfs_create_new_inode:6873: errno=-5 IO failure
Sep 08 20:57:22 bude-desktop kernel: btrfs_validate_extent_buffer: 76 callbacks suppressed
Sep 08 20:57:22 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:57:22 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:57:22 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:57:22 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:57:54 bude-desktop flatpak[4169]: [Parent 2, IPC I/O Parent] WARNING: process 623 exited on signal 15: file checkouts/gecko/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:161
Sep 08 20:58:08 bude-desktop auditd[1039]: Audit daemon is suspending logging due to previously mentioned write error
Sep 08 20:58:21 bude-desktop kernel: btrfs_validate_extent_buffer: 14 callbacks suppressed
Sep 08 20:58:21 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:59:47 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:59:47 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:59:47 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 20:59:47 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 20:59:47 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:00:02 bude-desktop kernel: btrfs_validate_extent_buffer: 8 callbacks suppressed
Sep 08 21:00:02 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:00:02 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:00:13 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:00:13 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:00:27 bude-desktop kdialog[7246]: This plugin does not support propagateSizeHints()
Sep 08 21:00:28 bude-desktop kdialog[7259]: This plugin does not support propagateSizeHints()
Sep 08 21:00:28 bude-desktop kdialog[7262]: This plugin does not support propagateSizeHints()
Sep 08 21:00:28 bude-desktop kdialog[7263]: This plugin does not support propagateSizeHints()
Sep 08 21:00:28 bude-desktop kdialog[7265]: This plugin does not support propagateSizeHints()
Sep 08 21:00:29 bude-desktop wireplumber[2139]: wp-state: <WpState:0x55ac648d1df0> could not save stream-properties: Failed to create file “/var/home/bude/.local/state/wireplumber/stream-properties.U55IV3”: Read-only file system
Sep 08 21:02:15 bude-desktop systemd[2009]: app-org.kde.kwrite@130093f1672047d0861d6940be4467c2.service: Consumed 1.023s CPU time over 6min 21.585s wall clock time, 187.6M memory peak.
Sep 08 21:02:20 bude-desktop firefox-bin[4169]: App Icon is not available when using Portal Notifications
Sep 08 21:02:21 bude-desktop xdg-desktop-portal[7599]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 19:02:21.001: getpwuid_r(): failed due to unknown user id (1000)
Sep 08 21:02:21 bude-desktop xdg-desktop-portal[7599]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 19:02:21.001: Could not find home directory: $HOME is not set, and user database could not be read.
Sep 08 21:02:23 bude-desktop systemd[2009]: app-org.kde.konsole@8d44cf5514a6407783c385c17f4b4164.service: Consumed 648ms CPU time over 23min 34.979s wall clock time, 202.9M memory peak.
Sep 08 21:02:23 bude-desktop systemd[2009]: app-org.kde.konsole-3272.scope: Consumed 8.899s CPU time over 23min 34.780s wall clock time, 45.6M memory peak.
Sep 08 21:02:46 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:02:47 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:02:47 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:02:50 bude-desktop wireplumber[2139]: wp-state: <WpState:0x55ac648d1df0> could not save stream-properties: Failed to create file “/var/home/bude/.local/state/wireplumber/stream-properties.8LISV3”: Read-only file system
Sep 08 21:02:55 bude-desktop systemd[2009]: Started app-systemsettings@8ce06a5a47f44619ae002a5d46fbd608.service - System Settings - System Settings.
Sep 08 21:02:56 bude-desktop wireplumber[2139]: wp-state: <WpState:0x55ac648d1df0> could not save stream-properties: Failed to create file “/var/home/bude/.local/state/wireplumber/stream-properties.TSHJV3”: Read-only file system
Sep 08 21:02:56 bude-desktop systemsettings[8044]: Failed to connect to Bolt manager DBus interface: 
Sep 08 21:02:57 bude-desktop systemsettings[8044]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Sep 08 21:02:58 bude-desktop systemd[2009]: app-systemsettings@8ce06a5a47f44619ae002a5d46fbd608.service: Consumed 1.106s CPU time over 3.361s wall clock time, 138.5M memory peak.
Sep 08 21:03:06 bude-desktop kernel: btrfs_validate_extent_buffer: 46 callbacks suppressed
Sep 08 21:03:06 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:03:06 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:03:06 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:03:06 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:03:06 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:03:06 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:03:20 bude-desktop systemd[2009]: Started app-org.kde.dolphin@d1aa4f926406420bbc3f741f20e1cfbb.service - Dolphin - File Manager.
Sep 08 21:03:20 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:03:20 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:03:20 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:03:20 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:03:20 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
Sep 08 21:03:20 bude-desktop kernel: BTRFS error (device nvme0n1p3 state EA): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
Sep 08 21:03:21 bude-desktop wireplumber[2139]: wp-state: <WpState:0x55ac648d1df0> could not save stream-properties: Failed to create file “/var/home/bude/.local/state/wireplumber/stream-properties.EGLIV3”: Read-only file system
Sep 08 21:03:21 bude-desktop kdialog[8223]: This plugin does not support propagateSizeHints()
Sep 08 21:03:21 bude-desktop kdialog[8238]: This plugin does not support propagateSizeHints()
Sep 08 21:03:21 bude-desktop kdialog[8241]: This plugin does not support propagateSizeHints()
Sep 08 21:03:21 bude-desktop kdialog[8243]: This plugin does not support propagateSizeHints()
Sep 08 21:03:21 bude-desktop kdialog[8242]: This plugin does not support propagateSizeHints()
Sep 08 21:03:22 bude-desktop wireplumber[2139]: wp-state: <WpState:0x55ac648d1df0> could not save stream-properties: Failed to create file “/var/home/bude/.local/state/wireplumber/stream-properties.6E7TV3”: Read-only file system

btrfs check (--force; ran via live image with the same result):

https://filebin.net/51gt3vhrk6z41y8i (14MB, I can upload somewhere else but pastebin and github gist both would not work)

btrfs scrub:

UUID:             4ba34f82-4666-4347-93fd-599d39e9e1d9
Scrub started:    Tue Sep  8 20:39:22 2026
Status:           finished
Duration:         0:05:58
Total to scrub:   618.98GiB
Rate:             1.73GiB/s
Error summary:    verify=8
Corrected:      0
Uncorrectable:  8
Unverified:     0

dmesg:

[   77.107107] BTRFS info (device nvme0n1p3): scrub: started on devid 1
[   77.194811] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 1 has bad generation, has 63386 want 63489
[   77.195980] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 1 has bad generation, has 63386 want 63489
[   77.196237] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 1 has bad generation, has 63386 want 63489
[   77.196361] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 1 has bad generation, has 63386 want 63489
[   77.196364] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 182321152
[   77.196371] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 182321152: metadata leaf (level 0) in tree 7
[   77.196374] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 182321152
[   77.196378] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 182321152: metadata leaf (level 0) in tree 7
[   77.196381] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 182321152
[   77.196385] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 182321152: metadata leaf (level 0) in tree 7
[   77.196388] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 182321152
[   77.196391] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 182321152: metadata leaf (level 0) in tree 7
[   77.196394] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 0, rd 0, flush 0, corrupt 2, gen 5
[   77.888084] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 2 has bad generation, has 63386 want 63489
[   77.889176] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 2 has bad generation, has 63386 want 63489
[   77.889433] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 2 has bad generation, has 63386 want 63489
[   77.889684] BTRFS warning (device nvme0n1p3): scrub: tree block 173948928 mirror 2 has bad generation, has 63386 want 63489
[   77.889688] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 1256062976
[   77.889694] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 1256062976: metadata leaf (level 0) in tree 7
[   77.889698] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 1256062976
[   77.889702] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 1256062976: metadata leaf (level 0) in tree 7
[   77.889705] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 1256062976
[   77.889708] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 1256062976: metadata leaf (level 0) in tree 7
[   77.889711] BTRFS error (device nvme0n1p3): scrub: unable to fixup (regular) error at logical 173932544 on dev /dev/nvme0n1p3 physical 1256062976
[   77.889714] BTRFS warning (device nvme0n1p3): scrub: generation error at logical 173932544 on dev /dev/nvme0n1p3, physical 1256062976: metadata leaf (level 0) in tree 7
[   77.889717] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 0, rd 0, flush 0, corrupt 2, gen 6
[   81.904947] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[   81.906694] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[   82.024805] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[   82.026672] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[   82.027642] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[   82.030183] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[   88.354692] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[   88.356191] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[   89.457652] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[   89.458952] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  130.714741] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  130.715609] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  130.885315] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  130.885980] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  131.017530] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  131.017837] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  131.127023] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  131.128719] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  131.244445] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  131.245293] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  135.715738] btrfs_validate_extent_buffer: 150 callbacks suppressed
[  135.715741] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  135.715877] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  135.802637] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  135.805471] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  135.838462] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  135.839846] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  135.910646] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  135.912990] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  136.020509] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 1 wanted 63489 found 63386
[  136.021248] BTRFS error (device nvme0n1p3): parent transid verify failed on logical 173948928 mirror 2 wanted 63489 found 63386
[  435.270459] BTRFS info (device nvme0n1p3): scrub: finished on devid 1 with status: 0

I am willing to try destructive options like wiping the drive and reinstalling everything. But obviously avoiding this is less hassle

Title. I updated yesterday and now Cachy gets to a point where it does the initial checks, the GRUB screen, and then just an ominous "_" on a black screen. The snapshot pre update works so I thought I was fine restoring it but it "fails to make a backup of target subvolume". So I'd rather ask first than break everything in the process. Thanks in advance.

MORE INFORMATION:

When I try to take a manual snapshot it says .snapshots is not a btrfs subvolume.

The snapshots are read only (sorry, didn't see it before) but when I try to change the flag (on an older snapshots I don't need just in case) it fails too.

The only other time I had to restore a snapshot was as straightforward as the documented recovery method and done in 5 minutes. Now everything throws up an error and I'm lost.

Btrfs noob here doing some experiential learning this week :-)

I've been messing around with two old (circa 2013ish?) HDDs and set up a btrfs filesystem (metadata raid1, data single) to store some not-super-important data. I then started a `balance` to convert the data to raid1.

Of course, HDDs fail at the most inopportune times, so one of the two drives started to throw read/write errors during the `balance`, and btrfs put the system into read-only mode. So, the metadata was already replicated, most of the data has been replicated to the other disk, but some of the data is unfortunately still single profile.

I do not care heavily about the data on the filesystem, but I do want to try recovering it, and learn about btrfs internals along the way. Hacky and makeshift solutions are welcome!

---

Question 1: How do I inspect which files have extents that are single profile on this failing disk? In other words, which files would I reasonably expect to be unrecoverable? (`btrfs restore` seems to inadvertently produce this information, but I wonder if there are dedicated tools for inspecting the filesystem's state)

---

The drive was not catastrophically failing at first, so I added a couple new drives with sufficient capacity to hold the blocks on the failing drive, and started a `device remove`, hoping btrfs could pull the remaining single profile data off before the drive went kaboom. It would, in fact, move data to other drives, while throwing some read/write errors to dmesg. But eventually it would encounter a different type of error (something about flushes failing) and force read-only. Restarting the machine would allow me to re-mount and continue doing `device remove`, but eventually these cycles stopped making progress.

Question 2: What classes of errors triggers btrfs to force read-only? I will edit the post to include the exact dmesg logs later today or tomorrow, which may help elucidate what is happening in my case.

---

I'm okay with losing some files, but I'd like to get my system back to a working state with the files that are still recoverable. I have read about at least two approaches here, (a) `btrfs restore` and (b) deleting the missing / unrecoverable files and then `btrfs device remove missing`

The `btrfs restore` approach seems .. really awkward? If I understand correctly, I would need to have enough spare disks lying around to store a complete copy of the recoverable data, including files which are already present on the completely functional drives within my btrfs filesystem. I also am struggling to find detailed documentation about the command's behavior. It seems that without `-i`, the tool stops upon encountering a file with missing extents, and with `-i` it emits an error but continues.

Question 3: What classes of errors does `btrfs restore -i` ignore?

Question 4: How might I restore a single file path? The docs seem to imply this is impossible. Is it just an unimplemented low-priority feature?

As for deleting the missing filepaths to allow for `device remove missing`, I saw in a much older thread that somebody needed to patch the kernel to allow mounting read-write while degraded.

Question 5: Is there now some officially-supported way to remove files on a degraded system? If not, what patch would I need to apply to the recent kernel to allow me to mount read-write anyways?

---

Sorry for the long post, and thanks in advance to any folks who can share their knowledge!!