> It's really hard to determine, you could try the following command to
> determine:
> # btrfs ins dump-tree -t extent --bfs /dev/nvme/btrfs |\
> grep "(.*_ITEM.*)" | awk '{print $4" "$5" "$6" size "$10}'
>
> Then which key is the most shown one and its size.
>
> If a key's objectid (the first value) shows up multiple times, it's a
> kinda heavily shared extent.
>
> Then search that objectid in the full extent tree dump, to find out how
> it's shared.
I analyzed it a bit differently but this should be the information we wanted:
https://gist.github.com/Atemu/206c44cd46474458c083721e49d84a42
Yeah...
Is there any way to "unshare" these worst cases without having to
btrfs defragment everything?
I also uploaded the (compressed) extent tree dump if you want to take
a look yourself (205MB, expires in 7 days):
https://send.firefox.com/download/a729c57a94fcd89e/#w51BjzRmGnCg2qKNs39UNw
-Atemu
