Puppy Linux Discussion Forum

I am using Gparted running in Fossapup64 9.5
It is Gparted v1.0.0

I used it to make a ext4 partition on a USB stick.
It says the process completed OK.

However, looking over the detail report of what it did.
I noticed this:

create new ext4 file system 00:01:22 ( SUCCESS )

mkfs.ext4 -F -O ^64bit -L '' '/dev/sdc1' 00:01:22 ( SUCCESS )

64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Creating filesystem with 7796480 4k blocks and 1949696 inodes
Filesystem UUID: 5687cb88-00b5-427b-abf4-ecbf2b045a09
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Do you think this is saying it started to make 64bit filesystem, but because support is not enabled, it did 32bit?

I am not totally sure this is really making a good working ext4 format.

mke2fs 1.45.5 (07-Jan-2020) is actually the mkfs that is used.
The file mkfs.ext4 is a symbolic link to mke2fs.

What do you think?

bigpup wrote:

Do you think this is saying it started to make 64bit filesystem, but because support is not enabled, it did 32bit?

Yes, 32bit. (the "-O ^64bit" means no-64bit)
Gparted reads the config file /etc/mke2fs.conf
In FossaPup, the config for ext4 in /etc/mke2fs.conf is (modified or perhaps older version):

        ext4 = {
		features = has_journal,extent,huge_file,flex_bg,metadata_csum,dir_nlink,extra_isize
		inode_size = 256
	}

Note that's without 64bit so a 32bit filesystem will be created.

Newer versions of e2fsprogs have /etc/mke2fs.conf with 64bit enabled:

        ext4 = {
		features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
		inode_size = 256
	}

On my system I have newest e2fsprogs installed, but a modified /etc/mke2fs.conf (without 64bit enabled)

Fred

OK,
Thanks for this info.
Clear as Puppy mud, now!
I learned something today!