On Sun, Jun 29, 2003 at 04:24:17PM +0200, Jaromir Dolecek wrote:
> Andreas Rohde wrote:
> > 2. and a strange floppy error message
> > /dev/fd0a works fine !!!!!!!!!!!! 
> > (one time a day -> no cron job etc ... )
> 
> Something ought be trying to access floppy. When these messages
> appear, can you try running
> 
> 	fstat | grep fd
> 
> to find out which particular process has the floppy device file open?
>  
> Jaromir
> 
> > fdcresult: timeout
> > fd0: timeout (st0 20<seek_cmplt> cyl 0)
> > fdcresult: timeout
> > fd0: timeout (st0 20<seek_cmplt> cyl 0)
> > fdcresult: timeout
> > fd0: timeout (st0 20<seek_cmplt> cyl 0)
> > fdcresult: timeout
> > fd0: timeout (st0 20<seek_cmplt> cyl 0)
> > fdcresult: timeout
> > fd0: timeout (st0 20<seek_cmplt> cyl 0)
> > fdcresult: timeout
> > fd0: timeout (st0 20<seek_cmplt> cyl 0)
> > fd0a: hard error reading fsbn 19 (st0 20<seek_cmplt> st1 0 st2 0 cyl 0 head 0 sec 2)
> > fdcresult: timeout

A related question:

Those messages above are the exact messages I've gotten when accidentally
trying to manipulate a floppy when there is none in the drive. They hang
EVERYTHING between messages while it tries to access the floppy drive. Isn't
there some way for the kernel to detect whether or not there is a disk in
the drive before trying to do things with it?

-Sean

-- 
/~\ The ASCII
\ / Ribbon Campaign                   Sean Davis
 X  Against HTML                       aka dive
/ \ Email!