On 2020/7/9 上午11:44, Hans von Stoffeln wrote:
> Hi,
>
> current situation is that the linux system df thinks the drive is full:
>
> /dev/mapper/HyVol002-hy002_data 3,0T 655G 0 100%
> /home/pyloor/data
This looks like a bug fixed by commit d55966c4279b ("btrfs: do not zero
f_bavail if we have available space"), which is fixed in v5.6, and
backported.
So what's your kernel version?
Thanks,
Qu
>
> But its not:
>
> Overall:
> Device size: 3.00TiB
> Device allocated: 655.07GiB
> Device unallocated: 2.36TiB
> Device missing: 0.00B
> Used: 654.34GiB
> Free (estimated): 2.36TiB (min: 1.18TiB)
> Data ratio: 1.00
> Metadata ratio: 2.00
> Global reserve: 512.00MiB (used: 0.00B)
>
> Data,single: Size:653.01GiB, Used:652.74GiB (99.96%)
> /dev/mapper/HyVol002-hy002_data 653.01GiB
>
> Metadata,DUP: Size:1.00GiB, Used:818.20MiB (79.90%)
> /dev/mapper/HyVol002-hy002_data 2.00GiB
>
> System,DUP: Size:32.00MiB, Used:96.00KiB (0.29%)
> /dev/mapper/HyVol002-hy002_data 64.00MiB
>
> Unallocated:
> /dev/mapper/HyVol002-hy002_data 2.36TiB
>
>
> I searched for the answer in the internet and a balance was suggested. I
> did it:
>
> btrfs fi balance start -dusage=5 .
> Done, had to relocate 3 out of 659 chunks
>
> I increment the value at usage to 95 but it says no chunks relocated.
>
> Thanks for the help and sry for the newbie question.
>
> Kind regards,
> Holger
Attachment:
signature.asc
Description: OpenPGP digital signature
