Your message dated Tue, 8 Jan 2013 09:45:53 -0500 with message-id <[email protected]> and subject line Re: Bug#697670: /sbin/fsck.ext2: fsck.X must warn about wrong filesystems has caused the Debian Bug report #697670, regarding /sbin/fsck.ext2: fsck.X must warn about wrong filesystems 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.) -- 697670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697670 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: e2fsprogs Version: 1.41.12-4stable1 Severity: normal File: /sbin/fsck.ext2 Hi, It can be a bug or not, or a wishlist, but this issue is pretty important since it is dangerous. Please if you do fsck.ext2 /dev/X of a ext3 instead of ext2. /dev/sdb1: UUID="XXX" TYPE="ext3" SEC_TYPE="ext2" root@debian07:~# date It might be checked or mentioned that the dev is not correct. You could add me a switch that might be useful for me and others. We all get old, and can be sometimes making mistake. You'll see in some years if you do not yet ;) Like an option --protect or --userinput, to prompt a read / inputchar y/n that we are sure of given op. An addional option might be the wisest one, + also since fsck is locked, linux must evolve (as sh locked from changes and large improvements). Sincerely, Pat -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages e2fsprogs depends on: ii e2fslibs 1.41.12-4stable1 ext2/ext3/ext4 file system librari ii libblkid1 2.17.2-9 block device id library ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libss2 1.41.12-4stable1 command-line interface parsing lib ii libuuid1 2.17.2-9 Universally Unique ID library ii util-linux 2.17.2-9 Miscellaneous system utilities e2fsprogs recommends no packages. Versions of packages e2fsprogs suggests: pn e2fsck-static <none> (no description available) pn gpart <none> (no description available) ii parted 2.3-5 The GNU Parted disk partition resi -- no debconf information
--- End Message ---
--- Begin Message ---On Tue, Jan 08, 2013 at 09:31:35AM +0100, patrick295767 wrote: > > It can be a bug or not, or a wishlist, but this issue is pretty > important since it is dangerous. What's dangerous about it? > > Please if you do fsck.ext2 /dev/X of a ext3 instead of ext2. If you run fsck.ext2 on /dev/X where /dev/X has an ext3 or ext4 file system, IT MAKES NO DIFFERENCE. In fact fsck.ext2, fsck.ext3, and fsck.ext4 are links to /sbin/e2fsck, and the behavior of e2fsck doesn't change depending on argv[0]. In fact normally I just run /sbin/e2fsck /dev/X just because I find it easier to type. > /dev/sdb1: UUID="XXX" TYPE="ext3" SEC_TYPE="ext2" > root@debian07:~# date > > It might be checked or mentioned that the dev is not correct. The dev is not correct? Huh? If you entered the wrong device, if it's mounted, e2fsck will already complain. If it's an unmounted ext[234] file system, e2fsck will check it. Nothing dangerous about that, even if it wasn't the device that you were intended to check. Feel free to ^C it. If it's a btrfs or xfs file system, e2fsck will already complain that it's not a file system that it doesn't know how to handle. Sorry, but I don't see a bug here at all, or even a valid wishlist item. - Ted
--- End Message ---
