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] Using 'zfs unmount -f' will unmount the file system, but I'd like to know why that was necessary. This situation appears to occur every night during a system test. The only peculiar operation on the errant file system is that another system NFS mounts it with vers=2 in a non-global zone, and then halts that zone. I haven't been able to reproduce the problem outside the test. Both systems are running S10U4. Any clues? Fred _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
