> > Jack, > > Yes, I may have to reboot, but I hoped there was some way to keep the > device from being busy so I could unmount it to run fsck. Otherwise, it > sounds like fsck can't be run from a system that has fully booted. > > Haines Sorry I didn't fully understand the question, Use the program called fuser to see what is using that drive,. There is a program called 'fuser N' where N is the file system you wish to check. example: fuser /etc /etc: 1092c 198c the numbers behind them are pid, do a ps aux | grep 1092 and that should return the program that is running in that filesystem. If it is owned by you, or isn't important trying killing it off with kill -9 1092 And any other process running on that file system, once there is no more process running on that drive, try umounting it then. If it is your root or swap drive, you probably shouldn't try this, as that will probably force you to reboot :) man fuser Jack
