Your message dated Sun, 7 Sep 2014 02:05:57 -0400 with message-id <[email protected]> and subject line Re: Bug#760706: mke2fs doesnt mention what type of system it just created has caused the Debian Bug report #760706, regarding mke2fs doesnt mention what type of system it just created to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 760706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760706 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: e2fsprogs Version: 1.42.12-1 Severity: wishlist File: /sbin/mke2fs # mke2fs /dev/bla Mentions a lot of things, but it might as well mention the most important thing too: what kind of filesystem (ext2, ext3 etc.) it just created (even thought the current default is indeed documented.)
--- End Message ---
--- Begin Message ---tags 760706 +wontfix thanks On Sun, Sep 07, 2014 at 12:39:09PM +0800, 積丹尼 Dan Jacobson wrote: > Package: e2fsprogs > Version: 1.42.12-1 > Severity: wishlist > File: /sbin/mke2fs > > # mke2fs /dev/bla > Mentions a lot of things, but it might as well mention the most > important thing too: what kind of filesystem (ext2, ext3 etc.) it just > created (even thought the current default is indeed documented.) The ext2, ext3, and ext4 file system drivers in the kernel are different implementations which support different subsets of file system features. And even now, since the ext4 file system in the kernel can support a superset of the features supported by fs/ext2/*.c and fs/ext3/*.c, many distributions have stopped compiling into their kernel "ext2" and "ext3", but instead are only compiling "ext4", and enabling a backwards compatibility feature so that when the user uses the command "mount -t ext3 ...", they really get the ext4 implementation. So talking about ext2, ext3, and ext4, as a specific kernel implementation is a well-defined notion. Talking about a file system *format* as being ext2, ext3, and ext4 --- not so much. The set of features enabled by default by a command such as "mke2fs -t ext3" has changed over time. Originally, it didn't include the dir_index feature; that was added later. There ar some new file system features such as "metadata_csum" which are currently under testing and while it is supported by the kernel, it's not supported by the e2fsprogs 1.42.x branch, but will be supported by e2fsprogs 1.43, and won't be included into as a file system feature enabled by default for several months after 1.43 is first released. Currently, mke2fs -t ext4 creates a file system with the following file system features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize ... while mke2fs -t ext2 creates a file system with a smaller set of features: ext_attr resize_inode dir_index filetype sparse_super ... and mke2fs -t ext3 creates a file system with: has_journal ext_attr resize_inode dir_index filetype sparse_super But you can do things like this: mke2fs -t ext3 -O extents /dev/sdXX ... and you can also do things like this: mke2fs -t ext4 -O ^resize_inode,^has_journal /dev/sdXX So to ask mke2fs to report "what type of file system" isn't something which is well defined, and in the end, will most likely engender more confusion than not. Cheers, - Ted
--- End Message ---
