Hi Erica, and welcome. You have come to the right list.
'lsof' will show you what prgrams are accessing the zip driver
Here is a quick example using a cdrom (expect similar behaviour for the
zip). In this case, as soon as I mount the cdrom, vmware/windows starts
using it. lsof reports this nicely
[root@kanga iso]# lsof /mnt/cdrom
[root@kanga iso]# mount /mnt/cdrom
[root@kanga iso]# lsof /mnt/cdrom
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
vmware 11890 root 11r BLK 11,1 181956 /dev/scd1
[root@kanga iso]# umount /mnt/cdrom
[root@kanga iso]# lsof /mnt/cdrom
[root@kanga iso]#
I doubt your version of mount is to blame. Try lsof.
hth
charles
On Tue, 24 Apr 2001, Erica B. Tanner wrote:
> Hello Redhat community! I am new to this list and hope it's the right
> list for the question I have.
>
> I just reinstalled Redhat 7.0 after a system crash and just finished
> patching my box. I am now having problems umounting my zip disks.
> Every flavor of umount that I use, even -f, gives me a 'busy' error,
> even though I know nothing is using it. I had to boot to run-level 1 to
> unmount the thing.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
