Package: dosfstools Version: 4.2-1.2 Severity: important File: /usr/sbin/fsck.fat Tags: upstream X-Debbugs-Cc: [email protected]
Dear Maintainer, The handling of all-bits-set directory entries is completely wrong. All-bits-set directory entries occur when recovering from power-loss writes to the directory sectors. These are not normal entries and need to be removed; however dosfsck tries to repair them instead. "Directory has non-zero size" "Start cluster is beyond limit(65535 > 60886)" Nope. It's not a directory as should be manifest as the volume label bit is set. There is no sensible interpretation of such entries. They should always be removed. https://github.com/joshudson/dossuperfloppy/raw/refs/heads/master/scantests/optionz.img.bz2 This is a test disk image. The filesystem starts on sector 63. This test case is actually testing for correct handling of VFAT entires on hostile filesystem alignment, so it looks a little bit different from my other, well-focused test cases. -- System Information: Debian Release: 13.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.57+deb13-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages dosfstools depends on: ii libc6 2.41-12 dosfstools recommends no packages. dosfstools suggests no packages. -- no debconf information
