Re: With Linux 5.5: Filesystem full while still 90 GiB free

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 2020/3/2 上午9:57, Etienne Champetier wrote:
> Hello Qu,
> 
> Le jeu. 30 janv. 2020 à 20:57, Qu Wenruo <quwenruo.btrfs@xxxxxxx> a écrit :
>>
>>
>>
>> On 2020/1/31 上午9:43, Matt Corallo wrote:
>>> This is a pretty critical regression for me. I have a few applications that regularly check space available and exit if they find low available space, as well as a number of applications that, eg, rsync small files, causing this bug to appear (even with many TB free). It looks like the suggested patch isn’t moving towards stable, is there some other patch we should be testing?
>>
>> That mentioned patch is no longer maintained, since it was original
>> planned for a quick fix for v5.5, but extra concern about whether we
>> should report 0 available space when metadata is exhausted is the
>> blockage for merge.
>>
>> The proper fix for next release can be found here:
>> https://github.com/adam900710/linux/tree/per_type_avail
>>
>> I hope this time, the patchset can be merged without extra blockage.
> 
> I see that there is a v8 of this patchset but can't find it in 5.6, is
> it targetted at 5.7 now ?
> https://patchwork.kernel.org/project/linux-btrfs/list/?series=245113

That's to be determined by David, I hope it could reach v5.7, but I
don't have the final say.

Thanks,
Qu

> 
> Thanks
> Etienne
> 
>> Thanks,
>> Qu
>>>
>>>> On Jan 30, 2020, at 18:12, Martin Steigerwald <martin@xxxxxxxxxxxx> wrote:
>>>>
>>>> Remi Gauvin - 30.01.20, 22:20:47 CET:
>>>>>> On 2020-01-30 4:10 p.m., Martin Steigerwald wrote:
>>>>>> I am done with re-balancing experiments.
>>>>>
>>>>> It should be pretty easy to fix.. use the metadata_ratio=1 mount
>>>>> option, then write enough to force the allocation of more data
>>>>> space,,
>>>>>
>>>>> In your earlier attempt, you wrote 500MB, but from your btrfs
>>>>> filesystem usage, you had over 1GB of allocated but unused space.
>>>>>
>>>>> If you wrote and deleted, say, 20GB of zeroes, that should force the
>>>>> allocation of metatada space to get you past the global reserve size
>>>>> that is causing this bug,, (Assuming this bug is even impacting you.
>>>>> I was unclear from your messages if you are seeing any ill effects
>>>>> besides the misreporting in df.)
>>>>
>>>> I thought more about writing a lot of little files as I expect that to
>>>> use more metadata, but… I can just work around it by using command line
>>>> tools instead of Dolphin to move data around. This is mostly my music,
>>>> photos and so on filesystem, I do not change data on it very often, so
>>>> that will most likely work just fine for me until there is a proper fix.
>>>>
>>>> So do need to do any more things that could potentially age the
>>>> filesystem. :)
>>>>
>>>> --
>>>> Martin
>>>>
>>>>
>>>
>>

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux