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

Mount failure results in mount flag not being cleaned up #175

Closed
Nikratio opened this issue Apr 22, 2022 · 1 comment
Closed

Mount failure results in mount flag not being cleaned up #175

Nikratio opened this issue Apr 22, 2022 · 1 comment

Comments

@Nikratio
Copy link
Contributor

It seems s3backer sometimes forgets to reset the "mounted" flag:

> /s3backer --blockSize=512K --size=50G nikratio-test-us/s3backer ~/tmp/mnt
s3backer: auto-detecting block size and total file size...
s3backer: auto-detection failed; using configured block size 512k and file size 50g
fusermount: option allow_other only allowed if 'user_allow_other' is set in /etc/fuse.conf

> sudo vim /etc/fuse.conf 

> ./s3backer --blockSize=512K --size=50G nikratio-test-us/s3backer ~/tmp/mnt
s3backer: auto-detecting block size and total file size...
s3backer: auto-detection failed; using configured block size 512k and file size 50g
s3backer: http://nikratio-test.s3-eu-west-2.amazonaws.com/s3backer/ appears to be already mounted (using mount token 0x2118b1a4)
s3backer: reset mount token with `--reset-mounted-flag', or use `--force' to override
@archiecobbs
Copy link
Owner

Should be fixed by 1fcfb80.

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

2 participants