mirror of https://github.com/vitalif/e2fsprogs
9e7da0bdc1
It seems that if we have the test_filesystem flag set on an ext3 filesystem(!) on a system which provides ext4, blkid gets confused. According to the current logic: * It's not an ext4dev filesystem, because the system provides ext4. * It's not an ext4 filesystem, because it has no ext4 features. * It's not an ext3 filesystem, because the test flag is set. In the end, it's nothing. blkid should return *something* that is mountable... I'm inclined to think that ext3 should be the right answer, if no ext4-specific features are set. This would mean just dropping the EXT2_FLAGS_TEST_FILESYS test in probe_ext3(), because ext4 & ext4dev probes have come first already. Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> |
||
|---|---|---|
| config | ||
| contrib | ||
| debian | ||
| debugfs | ||
| doc | ||
| e2fsck | ||
| ext2ed | ||
| include/nonunix | ||
| install-utils | ||
| intl | ||
| lib | ||
| misc | ||
| po | ||
| resize | ||
| tests | ||
| util | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| .missing-copyright | ||
| .release-checklist | ||
| ABOUT-NLS | ||
| COPYING | ||
| INSTALL | ||
| INSTALL.elfbin | ||
| MCONFIG.in | ||
| Makefile.in | ||
| README | ||
| README.subset | ||
| RELEASE-NOTES | ||
| SHLIBS | ||
| SUBMITTING-PATCHES | ||
| TODO | ||
| aclocal.m4 | ||
| configure | ||
| configure.in | ||
| depfix.sed | ||
| e2fsprogs.lsm | ||
| e2fsprogs.spec.in | ||
| version.h | ||
| wordwrap.pl | ||
README
This is the new version (1.41.3) of the second extended file system management programs. From time to time, I release new versions of e2fsprogs, to fix bugs and to make the utilities more robust. You can always find information about the latest version at the the e2fsprogs web page, which is: http://e2fsprogs.sourceforge.net The INSTALL file has instructions on building and installing e2fsprogs. Provisions for building Red Hat RPMs and Debian dpkg files are supplied as well. In case of bugs in these programs, please contact Ted Ts'o at tytso@mit.edu or tytso@alum.mit.edu. See the e2fsck man page for suggestions of what sort of information to include when submitting bug reports for these programs.