From: Qu Wenruo <wqu@suse.com>
To: Paul Graff <pj.world@gmx.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Stuck subvolume removal:
Date: Wed, 28 Jan 2026 19:19:15 +1030 [thread overview]
Message-ID: <8adc2517-a0fa-497d-ac3b-8700d39bb085@suse.com> (raw)
In-Reply-To: <121b0011-8076-4a0b-baff-384b6ec62986@gmx.com>
在 2026/1/28 19:12, Paul Graff 写道:
[...]
>> Unfortunately btrfs-progs doesn't have the ability to repair it yet,
>> I'll craft a branch of btrfs-progs with the repair ability soon.
>>
>> Meanwhile please prepare an environment to compile btrfs-progs.
>>
>> Thanks,
>> Qu
>
> Hi, I would like to ask if there is a solution to the "dropped ghost
> subvolume" the filesystem on machine here exhibits as of yet?
My bad, forgot to inform you about the fix.
In fact the fix is already merged into btrfs-progs, but not yet included
in any release.
If you can compile btrfs-progs, please fetch and compile the latest
devel branch:
https://github.com/kdave/btrfs-progs/tree/devel
After compiling the devel branch, you can use `btrfs check --repair` to
fix the problem, which will add back the missing orphan item for those
ghost subvolumes.
Thanks,
Qu
>
> -Thanks
>
> Paul Graff
>
>>
>>>
>>> [6/7] checking root refs (0:00:01 elapsed, 94 items checked)
>>>
>>> ERROR: errors found in root refs
>>>
>>> found 496776130741 bytes used, error(s) found
>>>
>>> total csum bytes: 465839608
>>>
>>> total tree bytes: 16133832704
>>>
>>> total fs tree bytes: 14983905280
>>>
>>> total extent tree bytes: 624771072
>>>
>>> btree space waste bytes: 3613129770
>>>
>>> file data blocks allocated: 1062495817728
>>>
>>> referenced 976540409856
>>>
>>> :~ #
>>>
>>>
>>>>
>>>> Thanks,
>>>> Qu
>>>>
>>> -Greatest Hopes
>>> Paul
>>>>>
>>>>> After passing,
>>>>>
>>>>> |:~> sudo btrfs subvolume sync / [sudo] password for root:
>>>>> hightower- i5-6600k:~> |
>>>>>
>>>>> the command returned to prompt very, very quickly.
>>>>>
>>>>> A second balance attempt results with the following output:
>>>>>
>>>>> |:~> sudo btrfs balance start / WARNING: Full balance without
>>>>> filters requested. This operation is very intense and takes
>>>>> potentially very long. It is recommended to use the balance filters
>>>>> to narrow down the scope of balance. Use 'btrfs balance start --
>>>>> full-balance' option to skip this warning. The operation will start
>>>>> in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1 Starting
>>>>> balance without any filters. ERROR: error during balancing '/':
>>>>> Structure needs cleaning There may be more info in syslog - try
>>>>> dmesg | tail hightower- i5-6600k:~> |
>>>>>
>>>>> |:~> dmesg | tail [93689.781162] [ T69656] BTRFS info (device
>>>>> dm-2): found 16 extents, stage: update data pointers [93690.667290]
>>>>> [ T69656] BTRFS info (device dm-2): relocating block group
>>>>> 1495819878400 flags data [93703.323923] [ T69656] BTRFS info
>>>>> (device dm-2): found 33 extents, stage: move data extents
>>>>> [93705.575991] [ T69656] BTRFS info (device dm-2): found 33
>>>>> extents, stage: update data pointers [93706.769453] [ T69656] BTRFS
>>>>> info (device dm-2): relocating block group 1494746136576 flags data
>>>>> [93725.570642] [ T69656] BTRFS info (device dm-2): found 39
>>>>> extents, stage: move data extents [93727.449779] [ T69656] BTRFS
>>>>> info (device dm-2): found 39 extents, stage: update data pointers
>>>>> [93728.465650] [ T69656] BTRFS info (device dm-2): relocating block
>>>>> group 60294168576 flags metadata|dup [93736.722689] [ T69656] BTRFS
>>>>> error (device dm-2): cannot relocate partially dropped subvolume
>>>>> 490, drop progress key (853588 108 0) [93750.594559] [ T69656]
>>>>> BTRFS info (device dm-2): balance: ended with status: -117
>>>>> hightower- i5-6600k:~> |
>>>>>
>>>>> Please see the following referenced, prior posting for stuck
>>>>> subvolume removal similarity. https://lore.kernel.org/linux-
>>>>> btrfs/9f936d59- d782-1f48-bbb7-dd1c8dae2615@gmail.com/
>>>>>
>>>>> Is there a patch for btrfsprogs? If so can the patch be merged?|
>>>>> |
>>>>>
>>>>> What are your thoughts on this?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
next prev parent reply other threads:[~2026-01-28 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 22:40 Stuck subvolume removal: Paul Graff
2025-11-13 22:54 ` Qu Wenruo
2025-11-14 19:38 ` Paul Graff
2025-11-14 19:55 ` Qu Wenruo
2026-01-28 8:42 ` Paul Graff
2026-01-28 8:49 ` Qu Wenruo [this message]
2026-03-01 15:47 ` Paul Graff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8adc2517-a0fa-497d-ac3b-8700d39bb085@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pj.world@gmx.com \
--cc=quwenruo.btrfs@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox