Re: btrfs thinks fs is full, though 11GB should be still free

Qu Wenruo
2023-12-22T00:53:16Z

[-- Attachment #1.1.1: Type: text/plain, Size: 1229 bytes --]

On 2023/12/22 09:24, Christoph Anton Mitterer wrote:
> On Fri, 2023-12-22 at 09:11 +1030, Qu Wenruo wrote:
>> The whole one is easier for me to check.
>
> https://drive.google.com/file/d/1-TJKoL85e23u5mJN0Nuoa9qyvgLRssFM/view?usp=sharing
>
> Should contain both (-t 257 and -e)

The situation is in fact simpler than I thought.

The original extent is 256M, and I believe that whole 256M is preallocated.

But later truncated to the current size, which is only 15+M.

Thus this explains the size problem.

But the problem comes on why defrag doesn't work.
I'll look into this during the holiday season, but I strongly believe
it's the PREALLOC inode flag.
We should take it seriously now.

Thanks,
Qu
>
>> But I still strongly recommend
>> to go "--hide-names" just in case.
>
> Checked it, and it's really only the prometheus filenames, all of which
> are completely non-sensitive... and it makes live easier if we can see
> the names.
>
>
>> Meanwhile you may want to upload the extent tree too (which can be
>> pretty large though), as my final step would need to check-cross
>> extent
>> tree to be sure.
>
> Here we go, thanks in advance.
>
>
> Cheers,
> Chris.
>

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7027 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]