Hi all, On 30-Mar-97 Dale Scheetz wrote: >> If you are in any of the mounted directories (including the top, e.g. >> /mnt), then umount would give this message and refues to unmount the >> device. >> >I don't know that this is strictly true. For instance, my fstab mounts >/usr from a seperate device, and, I assume, unmounts it during shutdown. >At the time of shutdown, all my users are logged in and sitting in their >user accounts. Now, I know that shutdown kills all the users off before it >does the unmounts, so by then they are not an issue. I assume all root >processes are killed off by then as well. >I had a problem recently of this type. I tried to unmount /cdrom and was >told that /dev/scd0 was busy. After going to each account logged in and >checking for processes using /cdrom, and finding none, I eventually logged >out all users but root at VC1 and was still unable to unmount. Since I >REALLY wanted the cd that was in the drive, I shut the drive off and then >back on. This let the drive open it's door so I could retrieve the cd, but >created problems for the system (i/o errors from df) until I rebooted. >I have learned since that I could probably have 'rmmod'ed the driver and >re-'insmod'ed it, but still have no idea why the system thought that the >device was busy. > >Waiting is,
The cause of my umount problem was bash-2.0-3_i386.deb. This problem was fixed when I downgraded it. Thanks everyone for your help, David
