Selon Moritz Muehlenhoff <j...@inutil.org>: > On Thu, Oct 16, 2008 at 06:04:53PM +0200, Jean-Michel wrote: > > Package: kernel > > Version: 2.6.24-etchnhalf.1-amd64 > > Severity: important > > > > > > Due to existing bugs I had with UDF in kernel 2.6.18, I use 2.6.24 for 8 > > days. > > With 2.6.18 some file were not copied/created, when my log file was mainly > > right. > > With 2.6.24 my log file is corrupt. > > > > Some monthes ago, I made one script which copy files to the 33 Gbytes > IOMEGA /dev/hda > > drive I formatted just before, with udf filesystem, in the same time it > > writes the text log file. > > > > Everithing looks nice, but begin of log file contains null bytes till > > around offset 0x06e3, when begin of this text file is missing. > > > > The log file is obtained by redirecting stdout. > > Sorry for the late reply. > > Is this error reproducible or does it only occur from time to time? > > If so, does it only show up with 2.6.24 and not with 2.6.18? > > Cheers, > Moritz
I do not remember if I added a workaround in the script or not. I just made some test: Now, files are written under a 2.6.24 kernel on 64 bits architecture with IDE drive. And looks like beeing readable. It also looks readbale from a 2.6.26 kernel on another 64 bits computer, via USB drive. I mean files can be readen without error, and log file does not contain any zero at begining. I did not check for vilidity of data nor is it is readble from an older kernel or a 32 bits architecture. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
