On 9 Jun 2002, ulrich mensfeld wrote:
Hallo Peter Osterlund ,
i copied the linux source-tree to the cdrw with ext2-fs now. My experiences on 'cp -a /usr/src/linux/* /mnt/cdwriter':
After a short time my system 'freezes' nearly completely for about 15
This probably happens because all of your memory is filled up with dirty buffers waiting to be written to the CDRW. This means that all processes
hmm, i have 512MB Ram and a swapspace of 256MB. Shouldn't that be enough for copying about 170MB?
Hmm, I guess it depends on how many other programs you are running. I have 1GB RAM and didn't see any freezes during the writing. The amount of available swap will probably not make a difference for this case. The problem is not that you are out of memory, it's just that all RAM is tied up to the cdrw and the only way to free it is to write it out to the excessively slow (compared to hard disks) CDRW device.
Another problem (or is that normal using ext2?): mounting the cdrw (after writing to it) in my cdrom instead of the burner, i couldn't see any files.
I would have thought it would work, but I don't have a CDROM drive to test this. Does the same thing work if you use the udf filesystem? Did the mount command succeed for the ext2 case or did you get some error message?
The mount command gave no error, also a df -H says the amount auf used and free! space on /dev/cdrom. But a ls -l /mnt/cdrom gives only an empty dir. With udf there are no problems to have access through the cdrom.
Are you sure it was really mounted as type ext2? Just run "mount" without arguments to see how it was mounted.
Is the 2.5 kernel worth a try? I'm running no system with special
What about the corrupted files? Is that managed in this version?
I don't know what's causing the corruption, so I don't know if it is fixed. What did the corruption look like in your case? In my case the
How could i determine the art of corruption? In the moment i'd done only the diff. Could you give me some scenarious, what to test and how?
Convert the corrupted and the original file with "hexdump" and diff the hexdump files. If you are using bash, you can do this in a single step like this: diff <(hexdump original_file) <(hexdump corrupted_file) Or just send me the corrupted files and tell me what kernel version you used for the test and I'll analyze this myself. -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340