[syslinux] ext4, boot error after writing irrelevant files on same partition

[Denys Fedoryshchenko]

After checking, it seems filesystem is not 64bit. Here is tune2fs 
output:

tune2fs 1.42.12 (29-Aug-2014)
Filesystem volume name:   GLOBALOS
Last mounted on:          /mnt/disk
Filesystem UUID:          291d7d67-cf5f-44a4-8297-204bcaf58dd6
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index 
filetype needs_recovery extent flex_bg sparse_super large_file huge_file 
uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              178464
Block count:              713467
Reserved block count:     7134
Free blocks:              570068
Free inodes:              178435
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      174
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8112
Inode blocks per group:   507
Flex block group size:    16
Filesystem created:       Tue May 19 06:36:27 2015
Last mount time:          Wed May 20 08:23:45 2015
Last write time:          Wed May 20 08:23:45 2015
Mount count:              11
Maximum mount count:      -1
Last checked:             Tue May 19 06:36:27 2015
Check interval:           0 (<none>)
Lifetime writes:          527 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      2600eba3-a1d5-48d3-92df-5c80f364136b
Journal backup:           inode blocks


On 2015-05-20 13:21, Denys Fedoryshchenko via Syslinux wrote:
> Yes, very possible. I will try to use -O ^64bit flag, and will check
> reliability.
> Thanks a lot!
> 
> On 2015-05-20 12:34, Ady via Syslinux wrote:
>>> This particular one - 3GB.
>>> Usually it is small. I faced this issue mostly on USB flash devices,
>>> sizing from 4GB to 16GB, but reproduced(not very reliably) now in 
>>> qemu
>>> as well, on 3GB partition.
>>> 
>> 
>> The size of your extN partition _might_ suggest that the problem could
>> be related to:
>>  "ext4 defaults to 64 bit, which extlinux can't reliably read"
>>  https://bugzilla.redhat.com/show_bug.cgi?id=1099237#c23
>> 
>> A: Because it messes up the order in which people normally read text,
>> especially the archives of mailing lists.
>> Q: Why is Top-posting such a bad thing?
>> 
>> Regards,
>> Ady.
>> _______________________________________________
>> Syslinux mailing list
>> Submissions to Syslinux at zytor.com
>> Unsubscribe or set options at:
>> http://www.zytor.com/mailman/listinfo/syslinux
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux