Re: A CD with errors (scratches etc.) blocks the whole system while

[Stephen Samuel]

I have a system with 2 hard disks (on separate controllers) and a CD-ROM
on the second controller (shared with the disk that, among other things)
handles /usr.

I took an old data CD, scratched  took a fork to it and mounted it.
I then started up MMX playing 'Hotel California' and tried to wc(1)
a 700K file on the CD.not too bad not too bad not too bad

Hotel California played fine, but trying to do an 'ls' of /usr
(same controller) took a LONG time..... (had to wait fnot too bad or the
CD to release the controller).

I could wc larg files in my /tmp directory, play music etc
before that WC came back -- I could do anything I wanted,
as long as I didn't need any data off of that second controller
(e.g. loading programs in /usr would die, since that HD shares
controller with the CD).

Given that I rarely use my CD ROM, it's fine having / and /usr
separated... On the other hand, if I was trying to read damaged CDs
with any regularity, I'd be making sure that the CD ROM drive was
sitting on it's own controller -- even if it meant putting all the
other IO on the system onto one IDE drive/controller.

> where the bulk of Linux system are running. Putting the CD on another
> cable is realistic (the system I hung does that) but putting the CD on IDE
> and the disk on SCSI is not cost effective compared to fixing the hang in
> software.

Note that this problem is a HARDWARE one -- not a software one.
It's kinda like trying to cross a Singapore highway... You can
do it faster, if you don't mind dealing with the nasty side of
a (data) bus. (read: SPLAT)

Bus error: car dumped.

(and if you think Linux is bad, try doing the same thing in
Windows!).

-- 
Stephen Samuel [phone]                [e-mail]
		   http://www.bcgreen.com/~samuel/
Powerful committed communication, reaching through fear, uncertainty and
doubt to touch the jewel within each person and bring it to life.