Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mounting via FUSE on Raspberry PI 4 (raspbianOS/debian) show all files as 0 bytes #40

Closed
ghost opened this issue Nov 14, 2020 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 14, 2020

Thank you for the addition of Fuse , it is working great on my x86/Mint desktop.
However when I mount my vault on Raspberry pi (debian buster on ARM) with the same settings all files in the vault show as 0 bytes.

Steps to reproduce:
I mount my cloud provider with Rclone.
rclone mount CloudProvider: ~/Cloudprovider --vfs-cache-mode writes

I then mount my vault with
java -jar cryptomator-cli --vault CloudVault=~/CloudProvider/CloudVault --fusemount CloudVault=~/CloudVaultMount

The vault unlocks and is browseable, but individual files show as 0 bytes and will not open.

Edit : additional info -

  1. Mounting with Webdav works fine, all files show correct sizes and are readable.
  2. The maven compile was performed on the PI, copying the JAR over to the Mint 20 x86 machine is working fine.
@ghost
Copy link

ghost commented Jan 31, 2021

+1 to this

raspberrypi% stat blah.pdf
  File: blah.pdf
  Size: 0               Blocks: 1612055706 IO Block: 4096   regular empty file
Device: 2ch/44d Inode: 4           Links: 1
Access: (0777/-rwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-01-30 17:15:08.360000000 -0800
Modify: 2021-01-30 17:15:08.360000000 -0800
Change: 1969-12-31 16:00:00.000000000 -0800
 Birth: -

Stat is showing zero bytes. Some tools I'm running are doing simple validation by comparing file sizes. Can revert to using dav fs but FUSE is proving to be much faster & reliable.

I compiled the jar on OSX under Java 12; just ran mvn clean install

@infeo
Copy link
Member

infeo commented Sep 4, 2024

We will rewrite the project in a different framework, throwing the old code away making this issue obsolete.

@infeo infeo closed this as completed Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant