On Fri, Dec 19, 2025 at 1:30 PM Christoph Hellwig <[email protected]> wrote: > On Thu, Dec 18, 2025 at 08:02:48PM +0800, Joanne Chang wrote: > > Thank you for the feedback. I will implement a > > _require_blocks_in_file helper in the next version. As far as I > > know, there isn't a generic way to query the block number limit > > across filesystems, so I plan to hardcode the known limit for > > F2FS within the helper for now. > > Oh, the limits is not the file size per se, so the number of blocks? > I.e. you can have a 64-bit i_size, but if the file isn't spare it > eventually can't fill holes? That really does seem like behavior > applications would not not expect, aka a bug.
Thanks for the reply. To clarify, I meant testing the architectural limit of blocks per file, not the current free blocks. Sorry for any confusion in my previous reply. The limit is indeed the maximum file size. However, since both the F2FS file size limit and the test's requirements are calculated as (block_number * block_size), I believe it is simpler to just test the block number. Best regards, Joanne _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
