Aborted: subvolume has no UUID

[amaccuish]

So reading the FAQ, it seems I am hit by "Aborted: subvolume has no UUID", in that my subvolume 5 does not have a UUID. How can I go about setting one?

/ Name: <FS_TREE> UUID: 86334f48-757e-4465-b8f3-5c2714764b9d Parent UUID: - Received UUID: - Creation time: 2020-04-30 20:19:14 +0100 Subvolume ID: 5 Generation: 44952077 Gen at creation: 0 Parent ID: 0 Top level ID: 0 Flags: - Snapshot(s):

[amaccuish]

I can see talk of it here but not sure it went anywhere..: https://www.spinics.net/lists/linux-btrfs/msg76016.html

[jwatt]

Your only hope of doing that would be to use btrfstune. No idea if it will work (or malfunction) when used with a filesystem that's in that state though.

Also, this isn't a btrbk issue.

[amaccuish]

Yes, not a btrbk issue but had hoped someone might have a solution. No answer on the btrfs mailing list https://lore.kernel.org/linux-btrfs/[email protected]/

Do you know anywhere else I could get help? I tried btrfstune but it changes the FS UUID, not the subvolume UUID.

[frinnst]

I found this thread when my backups stopped running. In my case it's related to btrfsprogs 6.1. Downgrading to 6.0 allows the backup to run. Obviously not the cause of the original issue since 6.1 was released in December 2022 - just thought i'd leave a comment.

[digint]

@frinnst you have hit a bug in btrfs-progs, see #519