Date: Fri, 24 Apr 2015 13:12:19 -0600 From: Gary Aitken <ah@dreamchaser.org> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: /cd0 held open but no files reported Message-ID: <553A9593.30500@dreamchaser.org>
next in thread | raw e-mail | index | archive | help
I have a situation I'd like some insights on... running 9.2 release on an AMD 64, X with xfce4 I mounted a CD from root: #mount -t cd9660 /dev/cd0 /cd0 Accessed some files on the CD using gimp. Exited gimp When I try to umount, I get the message: #umount /cd0 umount: unmount of /cd0 failed: Device busy However: #lsof /cd0 shows nothing but: fuser /cd0 /cd0: 2029 >From lsof: gvfsd-tra 2029 garya cwd VDIR 0,121 512 2 / gvfsd-tra 2029 garya rtd VDIR 0,121 512 2 / gvfsd-tra 2029 garya txt VREG 0,129 45792 4220202 /usr/local/libexec/gvfsd-trash gvfsd-tra 2029 garya txt VREG 0,121 105608 66081 /libexec/ld-elf.so.1 gvfsd-tra 2029 garya txt VREG 0,129 147752 1993838 /usr/local/lib/gvfs/libgvfsdaemon.so gvfsd-tra 2029 garya txt VREG 0,129 247312 1993832 /usr/local/lib/gvfs/libgvfscommon.so gvfsd-tra 2029 garya txt VREG 0,129 11832 1472099 /usr/local/lib/libgmodule-2.0.so.0.4200.1 gvfsd-tra 2029 garya txt VREG 0,129 1448336 1472091 /usr/local/lib/libgio-2.0.so.0.4200.1 gvfsd-tra 2029 garya txt VREG 0,129 308128 1472103 /usr/local/lib/libgobject-2.0.so.0.4200.1 gvfsd-tra 2029 garya txt VREG 0,129 1038952 1472095 /usr/local/lib/libglib-2.0.so.0.4200.1 gvfsd-tra 2029 garya txt VREG 0,129 52295 1471356 /usr/local/lib/libintl.so.8.1.3 gvfsd-tra 2029 garya txt VREG 0,129 334240 1468794 /usr/local/lib/libdbus-1.so.3.8.9 gvfsd-tra 2029 garya txt VREG 0,121 74176 99126 /lib/libutil.so.9 gvfsd-tra 2029 garya txt VREG 0,121 101048 99122 /lib/libthr.so.3 gvfsd-tra 2029 garya txt VREG 0,121 1369840 99098 /lib/libc.so.7 gvfsd-tra 2029 garya txt VREG 0,129 1084833 1469655 /usr/local/lib/libiconv.so.2.5.1 gvfsd-tra 2029 garya txt VREG 0,129 422120 1468248 /usr/local/lib/libpcre.so.1.2.3 gvfsd-tra 2029 garya txt VREG 0,129 28248 1471297 /usr/local/lib/libffi.so.6.0.4 gvfsd-tra 2029 garya txt VREG 0,121 82800 99128 /lib/libz.so.6 gvfsd-tra 2029 garya txt VREG 0,129 126280 2512671 /usr/local/lib/gio/modules/libgioremote-volu me-monitor.so gvfsd-tra 2029 garya txt VREG 0,129 205184 2512674 /usr/local/lib/gio/modules/libgvfsdbus.so gvfsd-tra 2029 garya 0r VCHR 0,19 0t0 19 /dev/null gvfsd-tra 2029 garya 1u VCHR 0,19 0t0 19 /dev/null gvfsd-tra 2029 garya 2u VCHR 0,19 0t0 19 /dev/null gvfsd-tra 2029 garya 3u PIPE 0xfffffe000cba2b60 16384 ->0xfffffe000cba2cb8 gvfsd-tra 2029 garya 4u PIPE 0xfffffe000cba2cb8 0 ->0xfffffe000cba2b60 gvfsd-tra 2029 garya 5u unix 0xfffffe01a501a2a8 0t0 ->0xfffffe01a501a000 gvfsd-tra 2029 garya 6u PIPE 0xfffffe01a501d5b0 16384 ->0xfffffe01a501d708 gvfsd-tra 2029 garya 7u PIPE 0xfffffe01a501d708 0 ->0xfffffe01a501d5b0 gvfsd-tra 2029 garya 8u KQUEUE 0xfffffe000cc98800 count=0, state=0x2 gvfsd-tra 2029 garya 9u unix 0xfffffe0184aea000 0t0 ->0xfffffe0184abdd48 gvfsd-tra 2029 garya 10u unix 0xfffffe0184abdd48 0t0 ->0xfffffe0184aea000 gvfsd-tra 2029 garya 11r VREG 0,121 2893 34721 /etc/fstab gvfsd-tra 2029 garya 12r VDIR 0,171 512 8748359 /hd2/home/garya/.local/share gvfsd-tra 2029 garya 13u unix 0xfffffe000caec000 0t0 /tmp/gvfs-garya-7d54udcg/socket gvfsd-tra 2029 garya 14r VDIR 0,171 512 8748371 /hd2/home/garya/.local/share/Trash gvfsd-tra 2029 garya 15r VDIR 0,171 16384 8750121 /hd2/home/garya/.local/share/Trash/files gvfsd-tra 2029 garya 16r VDIR 0,169 2560 2 /hd2/Downloads gvfsd-tra 2029 garya 17r VDIR 0,169 2560 2 /hd2/Downloads gvfsd-tra 2029 garya 18r VDIR 0,171 1024 2 /hd2/home gvfsd-tra 2029 garya 19r VDIR 0,171 1024 2 /hd2/home gvfsd-tra 2029 garya 20r VDIR 0,173 2560 2 /hd2/home/garya/Photos gvfsd-tra 2029 garya 21r VDIR 0,173 2560 2 /hd2/home/garya/Photos gvfsd-tra 2029 garya 22r unknown file system type: isofs gvfsd-tra 2029 garya 23u unix 0xfffffe01a5019aa0 0t0 /tmp/gvfs-garya-4y77tyna/socket gvfsd-tra 2029 garya 24r unknown file system type: isofs Can anyone give me a clue as to what's going on? I thought a device was only busy if a file was open on it, but clearly there are other ways to tie up a device. I presume it's tied up because gvfsd is looking for CDs being inserted, and apparently doesn't release the device after its last use. Just trying to understand what's going on; I know I can force an unmount using umount -f /cd0 After forcing a umount, the last entry and 3rd to last entry, with no TYPE and DEVICE reported, are missing, so I presume those are associated with /dev/cd0 Thanks for any pearls of wisdom... Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?553A9593.30500>