I can't see how this should be done on Linux without lsof lsof will help a lot if you have it. If you dont; maybe "find /cdmountpoint -print |xargs fuser -u" or somesuch will help... On a Sun box I would do a fuser the device node. eg fuser `mount |grep cdrom |awk { print $3 }` Another eg: For a Solaris box here - see what is using /opt : # mount / on /dev/dsk/c0t0d0s0 read/write/setuid on Mon Jan 17 09:48:26 2000 /usr on /dev/dsk/c0t0d0s6 read/write/setuid on Mon Jan 17 09:48:26 2000 /proc on /proc read/write/setuid on Mon Jan 17 09:48:26 2000 /dev/fd on fd read/write/setuid on Mon Jan 17 09:48:26 2000 /var on /dev/dsk/c0t0d0s3 read/write/setuid on Mon Jan 17 09:48:26 2000 /export/home on /dev/dsk/c0t0d0s7 setuid/read/write on Mon Jan 17 09:48:28 2000 /opt on /dev/dsk/c0t1d0s7 setuid/read/write on Mon Jan 17 09:48:27 2000 /opt2 on /dev/dsk/c0t2d0s7 setuid/read/write on Mon Jan 17 09:48:27 2000 /tmp on swap read/write on Mon Jan 17 09:48:28 2000 /home/qqq2 on /export/home/qqq2 read/write on Mon Jan 17 09:53:19 2000 /home/qqq1 on /export/home/qqq1 read/write on Tue Feb 15 16:17:43 2000 # fuser /dev/dsk/c0t1d0s7 /dev/dsk/c0t1d0s7: 13058ct 13553cto 13541cto 13539cto 8681to 8677to 8676o 8150cto 8116co 8115ct 8113ct 8112ct 8111cto 8093cto 8088c 6311c 12957t 12953o 12310to 12247o 12246t 12244t 12243t 12242to 11693to 11692o 10630to 10629to 10628to 10627to 10626cto 10625t 10617to 10616to 10615t 1165cto 7101cto 27978to 896to 838to 835to 807to 695t 479t 451t 403to 392to 391t 240to 218to 165t -----Original Message----- From: Steven T. Hatton [mailto:hattons@CPKWEBSER5.ncr.disa.mil] Sent: 22 February 2000 12:06 Cc: suse-linux-e@suse.com Subject: Re: [SLE] umount: /cdrom: device is busy Togan, Indeed that is usually the answer. Peter does raise a bigger question, even if you gave him the answer he sought. Is there a way to view information about who/what is accessing a resource such as a mounted fs? I don't know if there is, but it sure sounds handy if such a thing exists. Steve Togan Muftuoglu wrote:
Maybe you have acces to the cdrom ie if you are in a cdrom directory if so type cd then retry it should solve Togan Muftuoglu
Peter Onion wrote:
I'm sure this is an FAQ....
Is there a way to find what is causing umount to complian that "/cdrom:
device
is busy" ??
Peter.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/