I'm not sure if this is a known bug already, but, version 1.19 of mke2fs
doesn't handle the "-r0" switch properly. It sets the version to zero, but
goes right ahead doing version one stuff like filling the feature bitmaps,
serial number and activating sparse superblocks and the filetype feature.
Linux seems to get lucky because it loads the features bitmaps regardless
of the version number. However, in these version one disguised as version
zero volume, the features are *not* validated. This means that if such a
volume was mounted in an older kernel that didn't support sparse SB or
filetypes, you will get corruption because you'll skip through the feature
checking.
Daryl Low
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
