Theodore Ts'o

Many Linux distributions require that if you link against an external library, it must be linked in as a shared library. But that means that for programs like mke2fs which...

Can you provide a program which demonstrates how these problems would be demonstrated in real life (in particular for issue #2)?

To be honest, both look bogus. Sure, if you create a hashmap with size 0, this might cause a program to crash. But that's an application level bug. Calling it...

I'll be checking in a change to make your particular situation more obvious: % ./e2fsck /tmp/foo.img e2fsck 1.46.5 (30-Dec-2021) The filesystem size (according to the superblock) is 2097152 blocks The...

What I will probably do in the next major release is to deprecate the e2fsck -c and mke2fs -c options. The reason of this is something I explained a year...

How do you know that the directory is "broken"? Have you tried to force running e2fsck? If so, what does it report. Note that a directory entry with an inode...

I'm sorry you've managed to make your system not bootable. Out of curiosity, why were you trying to enable large_dir in the first place? Are you cutting and pasting from...

Hmm, I'm not able to reproduce it using a loop device: ``` # mkfs.xfs -f /dev/cwcc/scratch # mount /dev/cwcc/scratch /mnt # truncate -s 7E /mnt/foo.img # losetup /dev/loop0 /mnt/foo.img #...

Actually, if you wanted to create a file system that is, say 256 PB using ext4, you can do this by using the bigalloc file system option. This creates a...

Well, it was actually useful for me to take a look, because I *was* able to make mkfs.ext4 "spin" forever while creating a 256 PB image without the bigalloc option....