在 8/28/2025 9:44 AM, Chao Yu 写道:
> On 8/26/25 09:48, 王晓珺 wrote:
>> 在 8/25/2025 10:08 AM, Chao Yu 写道:
>>> On 8/20/25 15:54, Wang Xiaojun wrote:
This patch fixes missing space reclamation during the recovery process.
In the following scenarios, F2FS cannot reclaim truncated space.
在 8/25/2025 10:08 AM, Chao Yu 写道:
> On 8/20/25 15:54, Wang Xiaojun wrote:
>> This patch fixes missing space reclamation during the recovery process.
>>
>> In the following scenarios, F2FS cannot reclaim truncated space.
>> case 1:
>> write file A, size is 1G | CP | truncate A to 1M | fsync A | SPO
Hi Chao,
The combination of truncate and falloc complicates the recovery process.
For example, in the following scenario:
write fileA 2M | fsync | truncate 256K | falloc -k 256K 1M | fsync A | SPO
The falloc (256K, 1M) need to be recovered as pre-allocated space.
But in the following scenarios,
Hi Chao,
This patch will cause falloc to fail in the following scenarios.
write fileA 2M | fsync | truncate 256K | falloc -k 256K 1M | fsync A | SPO
So I will fix this issue in the next version of the patch.
Thanks,
On 8/8/2025 12:16 PM, Chao Yu wrote:
> Xiaojun,
>
> I just notice generic/483 wi
在 2025/8/8 12:16, Chao Yu 写道:
> Xiaojun,
>
> I just notice generic/483 will fail w/ this change, can you please take a
> look?
>
> Thanks,
Hi Chao,
OK, Thanks for pointing out the issue.
>
>
> On 8/7/2025 4:44 PM, Wang Xiaojun wrote:
>> This patch fixes missing space reclamation during the recov
