We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I'm using UtahFS on a Debian Buster box. I'm unable to have a stable filesystem. Sometimes it freezes, self unmount ...
And now, it doesn't want to mount anymore !
I run : utahfs-client -cfg backup-nas-utahfs.yaml -mount backup-nas-utahfs/ -v
utahfs-client -cfg backup-nas-utahfs.yaml -mount backup-nas-utahfs/ -v
And nothing happen anymore, no error displayed, no directory mounted... Command still run.
Nothing has changed in configuration, I always have .utahfs directory with metadata, pin & wal and S3 server is reachable.
How can I debug this ? How to get a stable file system ?
For information, config contains S3 data + :
keep-metadata: true wal-parallelism: 4 disk-cache-size: -1 mem-cache-size: -1 archive: false oram: false
The text was updated successfully, but these errors were encountered:
Using tcpdump, I can see UtahFS-client doing some S3 requests (https encrypted, I can't read them). Will it read/request the 5M+ objects it created ?!
Edit: it seems to be some PUT requests, hope wal is recovering...
Sorry, something went wrong.
Sorry for the noise, problem was on my S3 provider side ...
Glad you figured it out! Sorry for the delay
No branches or pull requests
Hi,
I'm using UtahFS on a Debian Buster box.
I'm unable to have a stable filesystem. Sometimes it freezes, self unmount ...
And now, it doesn't want to mount anymore !
I run :
utahfs-client -cfg backup-nas-utahfs.yaml -mount backup-nas-utahfs/ -v
And nothing happen anymore, no error displayed, no directory mounted... Command still run.
Nothing has changed in configuration, I always have .utahfs directory with metadata, pin & wal and S3 server is reachable.
How can I debug this ? How to get a stable file system ?
For information, config contains S3 data + :
The text was updated successfully, but these errors were encountered: