On 10/6/20 4:29 PM, Graham Perrin wrote:
lsof finds no open file.
Please be wary of lsof. I'm not sure it works on OpenZFS. The port
reaches into /usr/src for zfs headers in locations that don't exist
anymore to access kernel memory in /dev/kmem using structs that are
different in OpenZFS.
Hi!
> If the problem recurs: is it _ever_ sane to get nothing listed by lsof
> for a volume that can not be unmounted?
Use fstat -- this is part of the base system.
Maybe lsof does not catch every corner case ?
--
p...@opsec.eu+49 171 3101372Now what ?
_
On 11/10/2020 11:21, Graham Perrin wrote:
On 06/10/2020 21:29, Graham Perrin wrote:
lsof finds no open file.
How else might I tell why the device is busy?
Mobile hard disk drive, USB.
The same problem this morning,
root@momh167-gjp4-8570p:~ # zpool export Transcend
cannot unmount '/V
On 06/10/2020 21:29, Graham Perrin wrote:
lsof finds no open file.
How else might I tell why the device is busy?
Mobile hard disk drive, USB.
The same problem this morning,
root@momh167-gjp4-8570p:~ # zpool export Transcend
cannot unmount '/Volumes/t500': umount failed
root@momh167-gj
lsof finds no open file.
How else might I tell why the device is busy?
Mobile hard disk drive, USB.
--
root@momh167-gjp4-8570p:~ # zpool export Transcend
cannot unmount '/Volumes/t500': umount failed
root@momh167-gjp4-8570p:~ # lsof /Volumes/t500
root@momh167-gjp4-8570p:~ # zpool export Transc
