Subvolume won't delete

oldgeek — Mon, 20 Jul 2026 01:48:07 GMT

Awhile ago I had to revert to a pprevious setup due to a problematic upgrade. The recovery went well, but the process left the previous @ subvolume (which I renamed @_new) as a lingering subvolume in a group which includes @, @home, and a swap file. I've tried to delete @_new, both using the command line as well as Oshluvr's script for Dolphin, but no luck. I'm notified that the subvolume has been deleted, but it hasn't bee, I suspect this might be a problem of heirarchy, but since I am by and large ignorant of the structure of btrfs, I have no idea what to do. Any help would be appreciated.

30 s boot stall "Scanning for Btrfs filesystems"

jlittle — Mon, 06 Jul 2026 00:57:35 GMT

The NVMe SSD in my desktop died a few days ago, while it was in use (as the sender of a send/receive incremental backup). It was only a few years old. It is completely lifeless.

Using an old (2015) SATA SSD, I restored from a backup, and with some adjustments to /etc/fstab and a few subvolume creations (for .cache and snapper snapshots) Kubuntu 26.04 is running, albeit more slowly.

But during the boot, before plasma starts there is a step that stalls for about 30 s:

Code:

Scanning for Btrfs filesystems
registered /dev/sdc1
registered /dev/sdb6
registered /dev/sda2

(Those devices are those with btrfs on them, the last being the drive being booted.)

Can anyone explain this step? Removing the failed drive had no effect. Another install, a vanilla Kubuntu 26.04, on the same SSD does not have the problem.

Kubuntu Forums - BTRFS

Subvolume won't delete

30 s boot stall "Scanning for Btrfs filesystems"