On Tue, Apr 5, 2022, at 10:11 AM, Justin Forbes wrote:
>
> That list hasn't been edited in 5 years, but 256 bit inodes have been
> the ext default for a very long time unless you specifically request
> small.
In current Fedora CoreOS we have 128 bit inodes for /boot, and this appears to
be the default of `mkfs.ext4` for our chosen size of /boot:
[root@cosa-devsh ~]# truncate -s 384M /var/tmp/disk.img
[root@cosa-devsh ~]# mkfs.ext4 /var/tmp/disk.img
mke2fs 1.46.3 (27-Jul-2021)
Discarding device blocks: done
Creating filesystem with 393216 1k blocks and 98304 inodes
Filesystem UUID: 32e5f29f-5808-4feb-a8c2-83dfc3eef410
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
[root@cosa-devsh ~]# tune2fs -l /var/tmp/disk.img | grep 'Inode size'
Inode size: 128
[root@cosa-devsh ~]# rpm -q e2fsprogs
e2fsprogs-1.46.3-1.fc35.x86_64
[root@cosa-devsh ~]#
Ah but with a 512M disk I do get 256 bit inodes, I bet that's the difference.
>? I think the defaults for ext2 and ext3 even changed well over
> 10 years ago. The oldest disk I have here already has 256 bit inodes
> even for /boot
Or, maybe it's an Anaconda thing to override it?
Anyways...for now I may just get the PR merged to update FCOS's /boot.
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
