Package: fat-modules
Version: fat-modules-5.10.0-28-686-di
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: budheal...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I have this wand scanner and it uses microSD for storage, limited to
32GB. To transfer the image files, use USB or plug the SD into the
computer.
Before I upgraded to Bullseye, I encountered corruption - which I
decided it happened with I started to copy/etc. a new image file before
all of the thumbnails were showing. That's all of a hint I can give now.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I scanned a few pages, then plugged into the USB cable, at which point
the wand shows "USB" and Bullseye mounts the SD as a USB disk. The first
time on Bullseye, it worked okay. The second and afterwards, not so
okay.
The key before Bullseye was the thumbnails would show all black, usually
at the bottom of a folder. The images before the all black ones, usually
were apparently unaffected. By memory, there were screwy problems but
nothing like now.
Under Bullseye, just inserting or mounting the SD leads to corruption.
The files are are "readable" but not as proper images. When I insert the
SD into a Windows (10) laptop, it asks to check the filesystem and will
toss the unreadable images and leave the ones that are all black.
If I swap-and-swap with the Windows machine, there are no problems.
It looks to me like a minor annoyance (albeit a corruption but) which
has turned into an optimization that turned into a no starter bug. I'd
start by looking at things that could turn into competing write actions,
especially creating those mini-thumbnails.
* What was the outcome of this action?
The filesystem was not completely unusable. Only the image files that
were opened on the Linux desktop were affected. For a workaround, I
turned off showing the thumbnails and just copied the spool folder
(DCIM/100MEDIA, in this case) before looking at the image files (on the
Linux filesystem, not on the microSD).
* What outcome did you expect instead?
In any case, never corrupt existing data.
-- System Information:
Debian Release: 11.9
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-28-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
