Error: Process didn't exit successfully: `crates/redoxfs/target/debug/redoxfs-fuse build/i386-unknown-redox/debug/filesystem.bin build/i386-unknown-redox/debug/filesystem/` (exit code: 101)

Running `crates/redoxfs/target/debug/redoxfs-fuse build/i386-unknown-redox/debug/filesystem.bin build/i386-unknown-redox/debug/filesystem/`
redoxfs: opened filesystem build/i386-unknown-redox/debug/filesystem.bin
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
thread 'main' panicked at 'Unable to mount filesystem. Error Success (os error 0)', /home/thotheolh/.multirust/toolchains/nightly/cargo/registry/src/github.com-1ecc6299db9ec823/fuse-0.2.7/src/session.rs:50
note: Run with `RUST_BACKTRACE=1` for a backtrace.
error: Process didn't exit successfully: `crates/redoxfs/target/debug/redoxfs-fuse build/i386-unknown-redox/debug/filesystem.bin build/i386-unknown-redox/debug/filesystem/` (exit code: 101)
sync
fusermount -u build/i386-unknown-redox/debug/filesystem/
fusermount: failed to unmount /home/thotheolh/Desktop/Redox-OS/redox/build/i386-unknown-redox/debug/filesystem: Invalid argument
make: [build/i386-unknown-redox/debug/filesystem.bin] Error 1 (ignored)
rm -rf build/i386-unknown-redox/debug/filesystem/
nasm -f bin -o build/i386-unknown-redox/debug/harddrive.bin -l build/i386-unknown-redox/debug/harddrive.list -D ARCH_i386 -D TIME="`date "+%F %T"`" -ibuild/i386-unknown-redox/debug/ -ikernel/ -ifilesystem/ kernel/harddrive.asm

Some weird error when trying to mount fuse filesystem.

Do I need to open and log a support ticket for this issue on Github ?

I rebooted the entire Linux host OS I am using for the build and it strangely could build afterwards.

1 Like