macOS: hung during umount, crashes on mount after kill -9
constb opened this issue · 2 comments
constb commented
hi, I installed btfs from homebrew, this is the version:
$ btfs -v
btfs version: 2.18
libtorrent version: 1.2.0.0
OSXFUSE 3.8.3
FUSE library version: 2.9.7
fuse: no mount point
I have mounted and successfully downloaded a file from a torrent and then, when I did umount <dir>
, everything hung up: btfs, umount process, all processes trying to read that folder and its parent. I had to kill -9
it. Since i was running it with -d
switch, here's its log on exit:
listxattr / 0
unique: 5, success, outsize: 24
unique: 6, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 49399
getattr /
unique: 6, success, outsize: 136
unique: 2, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 49399
statfs /
unique: 2, success, outsize: 96
unique: 7, opcode: FORGET (2), nodeid: 3, insize: 48, pid: 49399
FORGET 3/1
DELETE: 3
unique: 3, opcode: FORGET (2), nodeid: 2, insize: 48, pid: 49399
unique: 4, opcode: DESTROY (38), nodeid: 1, insize: 40, pid: 49399
FORGET 2/1
DELETE: 2
unique: 5, opcode: INTERRUPT (36), nodeid: 0, insize: 48, pid: 49399
INTERRUPT: 4
umount: /Users/constb/Downloads/555: not currently mounted
Killed: 9
Now the problem is I cannot mount any torrent, here's what's happening:
$ btfs -d example.torrent 555
FUSE library version: 2.9.7
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 2, opcode: INIT (26), nodeid: 0, insize: 56, pid: 50397
INIT: 7.19
flags=0xf8000008
max_readahead=0x00100000
INIT: 7.19
flags=0x00000010
max_readahead=0x00100000
max_write=0x02000000
max_background=0
congestion_threshold=0
unique: 2, success, outsize: 40
unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 0
statfs /
unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 87
getattr /
unique: 2, success, outsize: 136
libc++abi.dylib: terminating with uncaught exception of type boost::system::system_error: invalid torrent handle used
unique: 4, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 87
statfs /
Abort trap: 6
I tried deleting its temp folder which is apparently ~/btfs
and this changed nothing…
manfredlift commented
Same issue here
johang commented
I have made some fixes in the macOS-fixes
branch. I don't have a macOS device so I can't test it.