cdrom to hd directory copy causes fs corruption!?!?!

by John W. Ros » Thu, 22 Aug 1996 04:00:00

Howdy...

Now that I have my cdrom (/dev/hdc) working, when I try to
copy a directory - or directories - the system hangs.
I reset the system and I get a ``file system error, run e2fsck
check manually'' message.
e2fschk is run and I recover the fs.
I can read files off the cd, but any multiple file copying
causes this hang.
Haven't gotten a chance to try WorkMan (audio) yet until I
get familiar with the plug n' pray utils for my SB16 PnP.
This happens with both the Slackware 1.3.20 and 2.0.12 kernels.
Anybody got any ideas on what could be causing this and how
to resolve it?

Thanx in advance,

Top

1. help: using "cp" causes data corruption when copying from drive to drive.

hello, i have a system with linux mandrake 8.0 on it with most of the
updates
except for the kernel update. i know that this isn't redhat but maybe you
can help anyway. I have customized the kernel to allow for ppp
being built as a module for poptop(pptp) vpn server services for windows
clients to access over the internet to this server. now the system is an
intel 815 chipset with piii 1ghz cpu 128mb ram and 2 hard disks on on each
channel one is the working drive a western digital u/100 7200 rpm 30gb drive
with the system and the home directories. the home directories are shared
over the network with samba. i have to shares setup for this network called
c and d. these shares on the file system look like this /home/public/c and
/home/public/d. the second drive in my system is an ibm 20gb 7200 rpm u/100
drive which i added to the system after i setup up the system. i mounted
the second drive as /backup and setup a cron job that ran a script that look
like this:
rm -r /backup/mon
mkdir /backup/mon
cp -fPRv /home/public /backup/mon

i have a file like this set up for everyday of the week set to run at 2:00
am in the morning. the script runs just like it's supposed to but, i get
lots of disk corruption. monday everything copies just fine. tuesday i get
some of the directories and wednesday i get even fewer and i'm lucky if it
even does anything on fryday. i was running fsck after i umount /backup and
then ran fsck /dev/hdc1 and it sould find tons of errors with inodes etc....
then i made sure cables were plugged in properly and i was using the correct
type of cables they were. this got to be a real problem. this is a 20gb
drive and the information i'm backing up is about 2.5 gb in about 33000+
files so i could backup 9 days without a problem, but it's not this way. is
their a solution to this, or work around?

i also tried a different route i used tar
script looked like this tar -cvzf /backup/mon.tgz /home/public

this command does exactly what i want it to, but when it's done i go into x
windows kde and try to use the archive agent and when i click on the file it
goes to read the file on /dev/hdc and it takes about 30 seconds and then it
stops and nothing comes up on the screen and even if i let it sit for
minutes it doesn't bring up a list of files and directories. if i backup
one of the home direcories example: c. Things work just fine. but i'm
worried about when these directories accumulate even more files. and this
disk corruption i get is really agrivating i don't know what i'm doing wrong
but i would be thankful for any help you can provide.

thanks,

joe

2. XFree86 Frequently Asked Questions

3. Cause of HD Block Corruption

4. picking"Display" subsections in "Screen" sections (XF86Config)

5. copying some directory tree to local HD with ftp

6. How to use syslog ?

7. 2.4.8 fs corruption and subsequent fs problems with links

8. Lost lpr Daemon

9. buffer layer error at fs/buffer.c:399 (Was incorrectly FS Corruption)

10. Copying from CDROM to floppy - why does HD go active?

11. HELP, testing file on CDROM w/o copying to HD