Package: dosfstools Version: 3.0.26-4 Severity: normal Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? On a file system not normally mounted that had been checked less than an hour earlier with the same options with the fsck from dosfstools 3.0.26-3, I encountered the following: fsck -yvV /dev/sdc1 fsck from util-linux 2.25.1 [/sbin/fsck.vfat (1) -- /dev/sdc1] fsck.vfat -yv /dev/sdc1 fsck.fat 3.0.26 (2014-03-07) fsck.fat 3.0.26 (2014-03-07) Checking we can access the last sector of the filesystem Boot sector contents: System ID "MSWIN4.1" Media byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per cluster 40 reserved sectors First FAT starts at byte 20480 (sector 40) 2 FATs, 32 bit entries 14324224 bytes per FAT (= 27977 sectors) Root directory start at cluster 1392 (arbitrary size) Data area starts at byte 28668928 (sector 55994) 3577496 data clusters (14653423616 bytes) 63 sectors/track, 128 heads 63 hidden sectors 28675962 sectors total / Bad short file name (). Auto-renaming it. Renamed to Reclaiming unconnected clusters. Checking free cluster summary. /dev/sdc1: 59384 files, 3478304/3577496 clusters victoria:/home/amarsh04# fsck -yvV /dev/sdc1 fsck from util-linux 2.25.1 [/sbin/fsck.vfat (1) -- /dev/sdc1] fsck.vfat -yv /dev/sdc1 fsck.fat 3.0.26 (2014-03-07) fsck.fat 3.0.26 (2014-03-07) Checking we can access the last sector of the filesystem Boot sector contents: System ID "MSWIN4.1" Media byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per cluster 40 reserved sectors First FAT starts at byte 20480 (sector 40) 2 FATs, 32 bit entries 14324224 bytes per FAT (= 27977 sectors) Root directory start at cluster 1392 (arbitrary size) Data area starts at byte 28668928 (sector 55994) 3577496 data clusters (14653423616 bytes) 63 sectors/track, 128 heads 63 hidden sectors 28675962 sectors total / Bad short file name (). Auto-renaming it. Renamed to Reclaiming unconnected clusters. Checking free cluster summary. /dev/sdc1: 59384 files, 3478304/3577496 clusters I have seen similar behaviour on one other filesystem (normally mounted, so could be getting corrupted by an unclean shutdown), but not on another filesystem (not normally mounted). * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.17.0 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dosfstools depends on: ii libc6 2.19-11 dosfstools recommends no packages. dosfstools suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012193139.5074.87736.reportbug@localhost