Hi, I'm interested in packet writing and I've benn following thil ML for some weeks. Now I had time to try it on my computer. I followed the instructions. 1.Quick setup of a cd-rw 2.Mounted and unmounted it without writing (I hope the messages it wrote are only debug stuff, not errors...) 3. Mounted it again and copy 20 Mb in three files (sorry, my writer is only a 2x and i had not the time to thy the source kernel tree) 4. Unmounted The data is all readable, through windows too. But data is corruped: i use cmp to compare the files and they were different. I've attached the log. Bye, Ludovico Cavedon lumaca82@inwind.it
On Mon, Apr 23 2001, Ludovico Cavedon wrote:
Hi, I'm interested in packet writing and I've benn following thil ML for some weeks. Now I had time to try it on my computer. I followed the instructions. 1.Quick setup of a cd-rw 2.Mounted and unmounted it without writing (I hope the messages it wrote are only debug stuff, not errors...) 3. Mounted it again and copy 20 Mb in three files (sorry, my writer is only a 2x and i had not the time to thy the source kernel tree) 4. Unmounted
The data is all readable, through windows too. But data is corruped: i use cmp to compare the files and they were different.
I've attached the log.
I'm amazed you got anything on disc at all, the problem is that sr doesn't get the capacity right. That's why you get entries like: Apr 22 22:25:22 pinco kernel: attempt to access beyond end of device Apr 22 22:25:22 pinco kernel: 0b:01: rw=0, want=710, limit=2 the kernel has the capacity set at 2 sectors, and denies reads beyond that completely. Does df show the right capacity when the disc is mounted? -- Jens Axboe
On Mon, Apr 23, 2001 at 07:10:24PM +0200, Jens Axboe wrote:
I'm amazed you got anything on disc at all, the problem is that sr doesn't get the capacity right. That's why you get entries like:
Apr 22 22:25:22 pinco kernel: attempt to access beyond end of device Apr 22 22:25:22 pinco kernel: 0b:01: rw=0, want=710, limit=2
the kernel has the capacity set at 2 sectors, and denies reads beyond that completely. Does df show the right capacity when the disc is mounted?
Well, I haven't seen this message any longer! The disc seems ok, but kook here, the used space ------------------------------------------ pinco:/usr/src/udf-cvs/udf/tools# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda4 6281212 4441200 1840012 71% / /dev/hda1 7746 6411 935 88% /boot /dev/hdc1 4210744 3915096 295648 93% /mirrors /dev/pktcdvd0 448320 343956 104364 77% /cdrom pinco:/usr/src/udf-cvs/udf/tools# ll /cdrom/ totale 21706 -rw-r--r-- 1 root root 1179808 apr 22 22:31 alsa-driver.tar.gz -rw-r--r-- 1 root root 20949741 apr 22 22:38 linux-2.4.3.tar.bz2 -rw-r--r-- 1 root root 92880 apr 22 22:31 lm-sensors-2.4.2_2.5.4-8+Custom.1.00_i386.deb drwxr-xr-x 2 root root 40 apr 22 22:20 lost+found ------------------------------------------- lost+found is empty. Where are those 320Mb??? However I deleted all files and copied them again and the udf source tree. All worked ok. I unmounted/mounted the device and my data was not corrupted!! As said, I did't see that message about the limit, but those 230Mb were still used and I saw this message:
Apr 23 23:48:39 pinco kernel: Device 0b:01 not ready: cmd=0, sector=73412, nr_sectors=60 Apr 23 23:48:43 pinco last message repeated 958 times
Now I'm compiling the new version and I will blank that cd. What sequence of commands of cdrwtool is equal to the "-q" option? Bye, Ludovico Cavedon lumaca82@inwind.it
participants (3)
-
Jens Axboe
-
Ludovico Cavedon
-
None