Skip to contentSkip to conversation

e2fsprogs: use default inode size for small fs

PATCH Mathieu Dubois-Briand 1 participant 2 messages Apr 8, 2021 – May 10, 2021 2 messages not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

Hi,

I'm not fully confident about some choices I made here, so I'm open to suggestions:
- I only apply the changes on the native build, so mkfs behavior on target will be unchanged. This may either be expected or unwanted.
- An alternative solution might be to change mkfs call in classes/image_types.bbclass to explicitly add '-I 256' if '$COUNT' is less than 524288 (512MB).

Also, bigger inodes means less usable space on partitions but this is mandatory to build images that may last after 2038.

Best regards,
Mathieu

#3 lore raw
In reply to a message not in the archive

Hi,

I don't see much enthusiasm for this patch. As I said, maybe the way I did it is not be the best one, but I'm open to any comment or request for modification.

I feel like the goal of this patch is important. Without it, small ext partitions generated with open embedded will not support any date beyond year 2038.

Is there any way I can help to progress with this issue ?

Best regards,
Mathieu