mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #694] invalid option -- 'b' #391
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#391
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 @Seungwoo321 on GitHub (Nov 28, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/694
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Version of s3fs being used (s3fs --version)
example: 1.00
Amazon Simple Storage Service File System V1.82(commit:566961c) with OpenSSL
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Version of fuse being used (pkg-config --modversion fuse)
example: 2.9.4
2.9.4
System information (uname -r)
command result: uname -r
4.9.62-21.56.amzn1.x86_64
Distro (cat /etc/issue)
command result: cat /etc/issue
Amazon Linux AMI release 2017.09
Kernel \r on an \m
s3fs command line used (if applicable)
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Details about issue
@gaul commented on GitHub (Nov 28, 2017):
Specify
-o dbglevel=infoinstead of-dbglevel=info.@ggtakec commented on GitHub (Jan 14, 2018):
I'm closing this issue, but if you have a problem yet, please reopen this.
And @gaul Thanks.
Regards,