Hi, The magic constant EXT_MAX_BLOCK = 0xffffffff in extents code is used in some places to return "invalid block number", and to set the extent length = "whole file" in other places. So with >= 16 TB fs we would prefer to use it differently. We can have EXT_UNSET_BLOCK = 1 to indicate "invalid block number" as it will never be valid block for allocation. And for "whole file" usecase we can continue using current EXT_MAX_BLOCK Regards, Girish -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
