Your message dated Thu, 21 Apr 2016 23:36:43 -0400
with message-id <[email protected]>
and subject line Re: Bug#821813: make more neutral messages lest user think you
are calling ext4 ext2, vfat fat
has caused the Debian Bug report #821813,
regarding make more neutral messages lest user think you are calling ext4 ext2,
vfat fat
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.)
--
821813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821813
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.43~WIP.2016.03.15-2
Severity: wishlist
File: /sbin/e2fsck
If in fstab one has lines like
UUID=c4414db0-65ee-4b6b-bb78-f672474821e5 /mnt/usb/cf auto
noauto,errors=remount-ro 0 0
UUID=0000-006F /mnt/usb/s1mp3 vfat
iocharset=ascii,shortname=mixed,noauto,noatime,nodiratime,user,fmask=133,uid=jidanni,gid=jidanni
0 0
but such devices are not plugged in, one will get
fsck.ext2: Unable to resolve 'UUID=c4414db0-65ee-4b6b-bb78-f672474821e5'
fsck.fat 3.99.0 (2015-05-16)
open: No such file or directory
1. One thinks "Hey, I spend a whole week researching how to make that an
ext4 drive, and now you are calling it a ext2!", Same with vfat / fat.
(Yes even though we haven't detected exactly which version of ext the
user has on the disk, which might still be in his cupboard, not plugged
in to the computer.)
Yes, even though they are just links to the same program, wouldn't it be
better to call them a more neutral name in the error message?
2. by the way, I later did mkdir /mnt/usb/s1mp3 but the message stayed
the same. So at least it should admit there is a directory there, even
if I didn't plug in a corresponding device. Ah maybe it is talking about
trying to open UUID=0000-006F, well then the message should be updated
to be the same as fsck."ext2"'s.
I suppose I should clone this to dosfstools...
--- End Message ---
--- Begin Message ---
On Tue, Apr 19, 2016 at 10:01:43PM +0800, 積丹尼 Dan Jacobson wrote:
> Package: e2fsprogs
> Version: 1.43~WIP.2016.03.15-2
> Severity: wishlist
> File: /sbin/e2fsck
>
> If in fstab one has lines like
> UUID=c4414db0-65ee-4b6b-bb78-f672474821e5 /mnt/usb/cf auto
> noauto,errors=remount-ro 0 0
^^^^
The problem is you've specified "auto" as the file system type. This
apparently causes fsck to blindly try a series of different fsck
programs: fsck.ext2, fsck.ext3, fsck.ext4, fsck.fat, etc.
> fsck.ext2: Unable to resolve 'UUID=c4414db0-65ee-4b6b-bb78-f672474821e5'
>
> fsck.fat 3.99.0 (2015-05-16)
> open: No such file or directory
>
> 1. One thinks "Hey, I spend a whole week researching how to make that an
> ext4 drive, and now you are calling it a ext2!", Same with vfat / fat.
> (Yes even though we haven't detected exactly which version of ext the
> user has on the disk, which might still be in his cupboard, not plugged
> in to the computer.)
>
> Yes, even though they are just links to the same program, wouldn't it be
> better to call them a more neutral name in the error message?
The "fsck.ext2:" and "fsck.fat" is not part of the error message per
se. Instead it's identifying the program which issued the error
message. This is standard Linux/Unix error behavior, so you know
where the error message came from. It's called that because fsck ran
the fsck.ext2 program.
This is not anything which is under e2fsprogs control, so I'm closing
this bug as invalid.
- Ted
--- End Message ---
