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
GCSF sometime unmounts itself. Looking at the logs it shows:
Jul 10 10:24:14 bwei-arch gcsf[29756]: thread '<unnamed>' panicked at 'called Option::unwrap()on aNonevalue', src/libcore/option> Jul 10 10:24:14 bwei-arch gcsf[29756]: note: Run withRUST_BACKTRACE=1 environment variable to display a backtrace. Jul 10 10:24:14 bwei-arch gcsf[29756]: WARN fuse::reply > Reply not sent for operation 114220, replying with I/O erro
Jul 10 10:24:14 bwei-arch gcsf[29756]: thread '<unnamed>' panicked at 'called
on a
value', src/libcore/option> Jul 10 10:24:14 bwei-arch gcsf[29756]: note: Run with
environment variable to display a backtrace. Jul 10 10:24:14 bwei-arch gcsf[29756]: WARN fuse::reply > Reply not sent for operation 114220, replying with I/O erro
(I am not sure if the above is relevant to the issue.)
Re-running gcsf mount resolves the issue.
gcsf mount
The text was updated successfully, but these errors were encountered:
No branches or pull requests
GCSF sometime unmounts itself. Looking at the logs it shows:
Jul 10 10:24:14 bwei-arch gcsf[29756]: thread '<unnamed>' panicked at 'called
Option::unwrap()on a
Nonevalue', src/libcore/option> Jul 10 10:24:14 bwei-arch gcsf[29756]: note: Run with
RUST_BACKTRACE=1environment variable to display a backtrace. Jul 10 10:24:14 bwei-arch gcsf[29756]: WARN fuse::reply > Reply not sent for operation 114220, replying with I/O erro
(I am not sure if the above is relevant to the issue.)
Re-running
gcsf mount
resolves the issue.The text was updated successfully, but these errors were encountered: