On Aug 12 02:59:38, frantisek holop wrote: > hi there, > > it seems that i have found the sequence to reliably > reproduce this problem. > > # mount /adata > # cd /adata > # vnconfig svnd0 install46.iso > # mount /dev/svnd0c /mnt > # umount /mnt > # umount /adata > umount: /adata: Device busy
/adata is your working directory now, as fstat will show you. > # vnconfig -u svnd0 > # umount /adata I don't believe it; /adata is still your working directory. I reproduced the above (/media is /adata), and I got this: # mount /media # cd /media # vnconfig svnd0 image.iso # mount /dev/svnd0 /mnt # umount /mnt # umount /media umount: /media: Device busy # fstat -f /media USER CMD PID FD MOUNT INUM MODE R/W SZ|DV root fstat 16372 wd /media 2 drwxr-x--- r 4608 root ksh 27271 wd /media 2 drwxr-x--- r 4608 # vnconfig -u svnd0 # umount /media umount: /media: Device busy # fstat -f /media USER CMD PID FD MOUNT INUM MODE R/W SZ|DV root fstat 26416 wd /media 2 drwxr-x--- r 4608 root ksh 27271 wd /media 2 drwxr-x--- r 4608 # cd .. # fstat -f /media USER CMD PID FD MOUNT INUM MODE R/W SZ|DV # umount /media Before you can umount the mount point, you need to both vnconfig -u the iso image, and get out of the directory. In particular, I don't believe the above sequence is real. Jan