Re: [RFC 1/1] btrfs/237: adapt the test to work with the new reclaim algorithm

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



On 22.08.22 12:49, Pankaj Raghav wrote:
> On 2022-08-22 11:40, Johannes Thumshirn wrote:
>> On 19.08.22 13:53, Pankaj Raghav wrote:
>>> Since 3687fcb0752a ("btrfs: zoned: make auto-reclaim less aggressive")
>>> commit, reclaim algorithm has been changed to trigger auto-reclaim once
>>> the fs used size is more than certain threshold. This change breaks this
>>> test.
>>>
>>> The test has been adapted so that the new auto-reclaim algorithm can be
>>> tested along with relocation.
>>
>> S-o-b missing.
> Oops. I hope it can be added before committing.
> Signed-off-by: Pankaj Raghav <p.raghav@xxxxxxxxxxx>
> 
>>
>> Thanks for doing this!
>> Tested-by: Johannes Thumshirn <johannes.thumshirn@xxxxxxx>
>>
> Thanks for testing it Johannes.
> 
> I did encounter an issue when I was trying out this test in a larger zoned
> device. I have explained the issue in my cover letter. I don't know if it
> is an issue with QEMU. As I don't have a physical PO2 device with me, did
> you see any of the issue I mentioned in the cover letter? If not, it might
> be an issue with the QEMU ZNS implementation.
>

I've been testing with my usual smoke test setup on null_blk with 128MiB 
zone size and capacity == size. Haven't encountered any issues with this.




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

  Powered by Linux