Your message dated Mon, 01 Jun 2015 01:19:35 +0000 with message-id <[email protected]> and subject line Bug#417639: fixed in dosfstools 3.0.28-1 has caused the Debian Bug report #417639, regarding fsck: please show note about read-only runs 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.) -- 417639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417639 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dosfstools Version: 2.11-2.1 Severity: normal File: /sbin/dosfsck What is the point of asking a question if in the end, you just "Leaving file system unchanged"? # fsck.vfat /dev/sdc1 dosfsck 2.11, 12 Mar 2005, FAT32, LFN /PALM/Programs/Plucker/dieyuanname300801132.pdb Duplicate directory entry. First Size 1637 bytes, date 16:03:20 Mar 30 2007 Second Size 1794 bytes, date 11:18:22 Mar 02 2007 1) Drop first 2) Drop second 3) Rename first 4) Rename second 5) Auto-rename first 6) Auto-rename second ? 6 Renamed to FSCK0000.REN Leaving file system unchanged. /dev/sdc1: 40 files, 44/7682 clusters Also perhaps offer 7) Do nothing. Oh, deep in the manual do we see If -a and -r are absent, the file system is only checked, but not repaired. -a or -r. Well then when if given no options, when the program starts, print "assuming -n, readonly mode, use -a ... to really cause changes next time." Let's guess that we need -w # fsck.vfat -w /dev/sdc1 -t and -w require -a or -r OK, then say that in the --help. # fsck.vfat -w -r /dev/sdc1 dosfsck 2.11, 12 Mar 2005, FAT32, LFN /PALM/Programs/Plucker/dieyuanname300801132.pdb Duplicate directory entry. First Size 1637 bytes, date 16:03:20 Mar 30 2007 Second Size 1794 bytes, date 11:18:22 Mar 02 2007 1) Drop first 2) Drop second 3) Rename first 4) Rename second 5) Auto-rename first 6) Auto-rename second ? 6 Renamed to FSCK0000.REN Perform changes ? (y/n) y /dev/sdc1: 40 files, 44/7682 clusters # fsck.vfat -w -r /dev/sdc1 dosfsck 2.11, 12 Mar 2005, FAT32, LFN Wrong checksum for long file name "dieyuan.htm020316342.pdb". (Short name FSCK0000.REN may have changed without updating the long name) 1: Delete LFN 2: Leave it as it is. 3: Fix checksum (attaches to short name FSCK0000.REN) ? 3 Perform changes ? (y/n) y /dev/sdc1: 40 files, 44/7682 clusters So we see that one needs a second pass to clean up after the first! # fsck.vfat -w -r /dev/sdc1 dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/sdc1: 40 files, 44/7682 clusters Maybe now all is well. Except of course one cannot find FSCK0000.REN anywhere. (That disk did not have a lost+found directory. Why not ask if OK to make one first if that is where such files will go?) Wait, if one does mount -t msdos /dev/sdc1 /mnt/usb/sd/ and comparing some find -ls's done under different mount -t's: 2350 16 -rwxr-xr-x 1 root root 1637 Mar 30 08:03 ./palm/programs/plucker/dieyua~1.pdb 2430 16 -rwxr-xr-x 1 root root 1637 Mar 30 08:03 ./palm/Programs/Plucker/dieyuanname300801132.pdb 2356 16 -rwxr-xr-x 1 root root 1794 Mar 2 03:18 ./palm/programs/plucker/fsck0000.ren 2436 16 -rwxr-xr-x 1 root root 1794 Mar 2 03:18 ./palm/Programs/Plucker/dieyuan.htm020316342.pdb So apparently we didn't lose anything. Odd about that "Duplicate directory entry." question. Anyway, so there you have my adventure. Telling me why what happened happened won't help, as I am a dullard. However, you might adjust the program to ask differently next time so that users won't get so confused.
--- End Message ---
--- Begin Message ---Source: dosfstools Source-Version: 3.0.28-1 We believe that the bug you reported is fixed in the latest version of dosfstools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Bombe <[email protected]> (supplier of updated dosfstools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jun 2015 02:33:30 +0200 Source: dosfstools Binary: dosfstools dosfstools-dbg dosfstools-udeb Architecture: source amd64 Version: 3.0.28-1 Distribution: unstable Urgency: medium Maintainer: Andreas Bombe <[email protected]> Changed-By: Andreas Bombe <[email protected]> Description: dosfstools - utilities for making and checking MS-DOS FAT filesystems dosfstools-dbg - utilities for making and checking MS-DOS FAT filesystems (debug) dosfstools-udeb - utilities for making and checking MS-DOS FAT filesystems (udeb) (udeb) Closes: 417639 753951 773885 Changes: dosfstools (3.0.28-1) unstable; urgency=medium . * New upstream version 3.0.28 - interactive repair mode is now the default for fsck.fat, ending confusion about the previous default mode that looked like interactive repair but never offered the option at the end to actually modify the filesystem (Closes: #417639) - fsck.fat now checks that the first cluster of a file is not 1, thereby also preventing a possible segfault (Closes: #773885) - 0xF0 is now allowed to be specified as media type for mkfs.fat (Closes: #753951) Checksums-Sha1: ab2140d3779d31a96afc30ed3d3b68d6c777f6c2 2010 dosfstools_3.0.28-1.dsc 1c6649b5ecd997e540dc1b6cbc3ecf98f34dd354 82980 dosfstools_3.0.28.orig.tar.xz a368f3232e79579b87a875855c165e77f8ce34b7 9492 dosfstools_3.0.28-1.debian.tar.xz 2daef2d07fdfd905806202d8679d31441cddfce4 157800 dosfstools-dbg_3.0.28-1_amd64.deb c2ae4c3fb79b13ad529ac41b5dcae29ad64c44a9 40660 dosfstools-udeb_3.0.28-1_amd64.udeb 696030deb0da4f8bcfb9eeddba740c0e9a778ab3 91486 dosfstools_3.0.28-1_amd64.deb Checksums-Sha256: b73d02e71f48804dcdee713ddc05aef964d931239c2870fa275b994cb0b59ade 2010 dosfstools_3.0.28-1.dsc ee95913044ecf2719b63ea11212917649709a6e53209a72d622135aaa8517ee2 82980 dosfstools_3.0.28.orig.tar.xz e03e97a8d7ed02906a2541afb96c83afb2f6af3ba3cf13e631827c508ce9e76c 9492 dosfstools_3.0.28-1.debian.tar.xz 00c8eb4d3bcb2b5b819f2563289431e02eddf9a18cd81b8758500ea426709d1b 157800 dosfstools-dbg_3.0.28-1_amd64.deb 9dc801bd41071c30ebc2ba999b26c3ca394143bc43c317c7e4baa58b246ce65d 40660 dosfstools-udeb_3.0.28-1_amd64.udeb b6261e5b79c610e0e3b2438f6750cf685addb180231e531ad09d5f91681d8895 91486 dosfstools_3.0.28-1_amd64.deb Files: 7a109522c4071f5098688035a3193e9d 2010 otherosfs optional dosfstools_3.0.28-1.dsc 6a047a6c65186b9ebb1853709adb36db 82980 otherosfs optional dosfstools_3.0.28.orig.tar.xz 62dafe523967552fdd38f2cf3606a632 9492 otherosfs optional dosfstools_3.0.28-1.debian.tar.xz 1e8af6efbe64efedd1c2eb75f45d614a 157800 debug extra dosfstools-dbg_3.0.28-1_amd64.deb bad8e73741a27c06811217d5162fe84e 40660 debian-installer optional dosfstools-udeb_3.0.28-1_amd64.udeb 9bb74732e98f9891e17f5ee0e8a72625 91486 otherosfs optional dosfstools_3.0.28-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVa7DJAAoJEDFkcFsdox1Mzz8P/1/NY/UwSMfdQfg1Al660mM6 Al1BxjjSCZEEPM7Xgr0XYzBF+EDc0k3YEJa3U+LgCp7WOAbY4tcBT9Chxk8beI3a Nq7BXkhmcMRy2HvoHWzADkcz1AQFzOty87/kJuDk70SNXTjFu3WBr25+1CvaU/T2 gTLRdYdEaxw2eKAdpZDH3z+ffWRjdGVXDpLdbTbjlZ0ZAzG9I7VIlLMBH61h0IWl Sp28pzUZIgYDX5gl9mSyuvPe+K7A3rK6GjpofYwvh8QOIl3TbZT81kSAV9FfY3FP tk2YUuCftGR13jrluR3kdctZjYa0LVCwWKM9mkXJSdsmDvBrX43WEwczyzXPzFpQ XUf49AW1T8AIwjHakJbSh6N0nXQzMzZKcKxQMKHB9ZLQWBifTLjg4FqjpJjOduta y+273v4ez9PmG93nGHwdBlU5hUDRWosI5euVYOndK5WZqGc+2iiSN4QA3pzTgWRC ntaGvTOOyAxxmWngXW8rKZc3PIEbQlJBk90HNWBv9P+yzjqkgBQcCTK2+Xs+uQbF +3mMd/CTaLNpfo84s/uH6WTVj0AU4cDr7pdHPzsaixMSRF0k/umdjh4zoz2Fv6A7 UOOVaWj2XHKf0cB6+j8lFs5qNIioq5hFn3ogcz4smI6q0mMas70t/BCPlDe57RbK IbruJmeSNPA62XGHXZdD =Utro -----END PGP SIGNATURE-----
--- End Message ---
