Ryurick M. Hristev wrote:

> 'fuser -muv <dir>' will tell you who is using what.
> Ocasionally you may get a hang in the kernel, if so then
> you are out of luck (i.e. need rebooting)

If it is the kernel, do you get this (/dev/hdd is mounted on /cdrom so I 
tried both):

smurf:~# fuser -muv /cdrom
smurf:~# fuser -muv /dev/hdd
smurf:~# umount /cdrom
umount: /cdrom: device is busy
smurf:~#

I don't use the drive very often so the reboot can wait until I get a 
more pressing reason.

I think this may have been what killed my Windows boot this evening.  
/cdrom is exported by Samba and it wasn't until I commented out the 
relevant lines in smb.conf that Win would successfully boot up.

I ended up killing the install last night since it was so painfully slow 
on the 8Mb 486 (it required swap just to run the setup script).  I shoved 
the drive into the P133 and it was quite happy until it ran out of space. 
 500Mb isn't enough, and I didn't even install X!  I think I'll skip the 
kernel source... I'll bake a fresh kernel on the other box.

Cheers,


- Dave

http://www.digistar.com/~dmann/ (out of date)


Reply via email to