genext2fs creates revision 0 filesystems instead of revision 1

[Martin Emrich]

Binary package hint: genext2fs

I had a hard time finding out why extlinux (from the syslinux package) did not like the images I generate with genext2fs. I finally found out that genext2fs creates ext2 revision 0 filesystems (which seem to be deprecated since Linux 1.2 or so).

The only way I found to "upgrade" the FS to revision 1 is to run "tune2fs -j <image>" to add a journal, and then run "fsck.ext3 -f <image>" to set the revision level.

The problem can be verified using "tune2fs -l <image>", which prints out the revision number.

[Ricardo Salveti (rsalveti)]

This is actually expected on the current genext2fs implementation. Currently it's declaring and filling only the required fields for revision 0.

For revision 1 filesystems we also have volume name, UUID and some other extra fields. This is listed to be implemented in the TODO file from genext2fs project, but I believe that will never be done, as running fsck to fix the values is much easier from a user perspective.

[Ricardo Salveti (rsalveti)]

Marking this as Invalid as this is the default behavior of the software. Please reopen it if you don't agree with the solution.