Bug#594753: some files with no extension are corrupted when burnt on CD

[Mathias Kende]

severity 594753 grave
found 594753 2.30.3-2
stop

I think that I am seeing the same issue. I burnt a data CD with brasero
which reported the operation as being successful. Some of the burnt file
names were long and I asked brasero _not_ to keep a strict windows
compatibility when it asked the question.

But some of the files are corrupted on the disc : their size is
correctly reported (as per the original file) but they are empty or
contains only zeros:

$ ls -lh README
-r--r--r-- 1 root root 10K 11 janv. 22:21 README
$ cat README
$ hexdump -C README 
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000027f0

All the faulty files have exactly the same content. And it appears to be
the same when they are read on Windows XP (in an other computer, so with
a different CD drive), even though there the file are shown as full of
white space (with their correct size), but I did not check with an
hexadecimal viewer, so this could just be a glitch of the viewer.

The problematic files all have file names without extension (like
"README"), but not all the file without extension are corrupted. In fact
all the file without extension on the disc are corrupted except those
whose names were "md5" (so i was able to discover the bug...).

Also, when I try to read the faulty CD in my drive (the burner), the
drive will sometime crash (with approximately 50% chance): I insert the
CD in the drive, nothing happens in the computer (the CD is not
mounted), except that I am seeing messages in kern.log similar to those
of the bug reporter (I'm attaching some relevant part of kern.log). If I
try something like manually mounting /dev/sr0 or trying to eject the CD,
then the drive start making an awfull noise (I have never heard a CD
drive makes such a noise so I can't describe it), but nothing else
happens. The only way to return to a proper operation mode of the drive
seems to restart the computer.
Other CD (or the faulty one with half a chance) are working fine.

I'm raising the severity to grave because this bug makes one believe
that some files are properly backed-up while they are not, and could
possibly lead to a data-loss. 

My CD drive/burner is an LG drive and is reported in dmesg as being a:
ata3.00: ATAPI: HL-DT-ST DVDRAM GSA-H10N, JL10, max UDMA/33
I am running Debian Squeeze AMD64.

I burnt the same data with an other burner on an other computer (but
with the exact same Debian Squeeze), and the result was correct (no file
corruption). I burnt the data three time on the problematic computer
with always the same result.

I burnt other files on CD to test the burner and all the burnt CD are
correct, including some with file with no extension and with (on the
sale CD) other file with very long filename causing brasero to disable
(at my request) a strict windows capatibility of the disc. So my burner
seems to work correctly (also, I never had any problems with it).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: kern.log
Type: text/x-log
Size: 10444 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20110112/4fb56242/attachment-0001.bin>