mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #732] Mounting S3 Bucket Fails with "same bucket(default)" error #416
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#416
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dresswithpockets on GitHub (Mar 13, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/732
Additional Information
Version of s3fs being used (s3fs --version)
1.83
Version of fuse being used (pkg-config --modversion fuse)
2.9.4
System information (uname -r)
4.4.0-1052-aws
Distro (cat /etc/issue)
Ubuntu 16.04.3 LTS
s3fs command line used (if applicable)
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
Details about issue
Mounting S3 Bucket at command line using s3fs (as shown above) prints off the error
s3fs: same bucket(default) passwd setting found in passwd file.and doesnt mount.Mounting via fstab and running
mount -aproduces the same error.@dresswithpockets commented on GitHub (Mar 13, 2018):
I solved this. The problem was that there are multiple entries in the passwd file that match the default/no bucket.
Ultimately the confusion from this issue came from the fact that the error message is not very helpful. I managed to decipher what the error message meant by looking at the code that leads to that message:
I'm going to submit a PR for this issue to make this message more descriptive and helpful.