Re: Bug reporting
Hi,
On Tue, Jan 06, 2026 at 06:01:12PM +0000, Lars Olsson wrote:
> It also happens if I instead try to copy the files made on Windows to
> my Debian computer via scp (haven't tested with ftp).
This seems to be the simplest of all your error cases as if I've
understood correctly it is a single file transferred from Windows to
your Debian on a local filesystem without using any
archival/compression/encryption tool like 7z.
I suggest doing this:
1. Take a large file that's on your Windows machine.
2. Do a checksum of it with some tool like md5sum, sha256sum or whatever
Windows has.
3. Copy the file to your Debian machine using scp, sftp or rsync. It
should be sent to a local filesystem of some typical type like ext4
or btrfs,
4. Run the same checksum on the file that's now on your Debian machine.
If the checksums match then you haven't managed to reproduce your
issue. Try to work out what is different between the above and what you
do when you do see the problem. Try again.
If the checksums do not match then it seems you have experienced data
corruption at some point. Off the top of my head these points could be:
a) Some aspect of reading data from your Windows machine. Could perhaps
be debunked by obtaining files from some other source where you know
the checksum and seeing whether the corruption does or does not
happen. If it still happens then it's not the Windows machine.
b) In your network. Seems unlikely since a TCP stream like scp should
have its own checksumming.
c) In your Debian machine's hardware like storage controller, drives or
memory. Seems unlikely since your operating system would just totally
malfunction relatively quickly.
d) A bug in your Debian machine's kernel.
There are no doubt other possibilities but if you can replicate to this
stage then I think it's worth reporting a bug against the Debian kernel
package. To do this ruyn:
$ reportbug kernel
while booted into the kernel you replicate this with.
> The error should be easy but rather time-consuming to reproduce. Just
> do something like below on a huge folder with thousands of files. The
> archive files I make are put on a usb-drive and I tested with two
> different usb-drives (actually one SSD in a cheap cabinet and one M.2
> NVMe in an ASUS TUF cabinet, highly recommended).
Try to exclude USB from your tests. Transfer things over the network to
local filesystems on storage that's attached by some more traditional
means like SATA, M.2, SAS, etc. I have seen a LOT of USB storage issues
like this.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Reply to: