Richard Elling wrote: > Fred Oliver wrote: >> I am having trouble destroying a zfs file system (device busy) and >> fuser isn't telling me who has the file open: >> >> # zfs destroy files/custfs/cust12/2053699a >> cannot unmount '/files/custfs/cust12/2053699a': Device busy >> >> # zfs unmount files/custfs/cust12/2053699a >> cannot unmount '/files/custfs/cust12/2053699a': Device busy >> >> # fuser -c /files/custfs/cust12/2053699a >> /files/custfs/cust12/2053699a: >> >> # (cd /files/custfs/cust12/2053699a && fuser -c .) >> .: 10383c [fuser itself or shell] >> > > shell? Is your CWD on that file system? Usually when I do this > it is because I was somewhere and su'ed which leaves a shell > with the CWD where I su'ed. > -- richard
I just meant that in this example [cd foo && fuser], either the subshell exec'ing the fuser command or the fuser process itself is process 10383, and neither one lasts long enough to easily identify which. Fred _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
