starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #259] Strange Bug: Creating folder "showshow" results in unwriteable folder. #134

New issue

Closed

opened 2026-03-04 01:42:29 +03:00 by kerem · 7 comments

kerem commented

2026-03-04 01:42:29 +03:00

Owner

Originally created by @Cat5TV on GitHub (Sep 10, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/259

Encountered a very strange bug (I'm assuming it's a bug) in creating a folder specifically named "showshow". No matter what, if I make a folder with that name under s3fs, I get a folder where NO FILE can be written. All files placed in this folder simply end up being 0 bytes (glad I caught this!)

It is not a Linux permissions issue.

Check it out:
user@server:/s3fs-mountpoint$ mkdir showshow
user@server:/s3fs-mountpoint$ cd showshow
user@server:/s3fs-mountpoint/showshow$ touch test
touch: closing `test': Bad file descriptor
user@server:/s3fs-mountpoint/showshow$ cd ..
user@server:/s3fs-mountpoint$ mkdir show
user@server:/s3fs-mountpoint$ cd show
user@server:/s3fs-mountpoint/show$ touch test
user@server:/s3fs-mountpoint/show$ ls
test
user@server:~/s3fs-mountpoint/show$

Weird eh? Why would this be?

Thanks!!

Originally created by @Cat5TV on GitHub (Sep 10, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/259 Encountered a very strange bug (I'm assuming it's a bug) in creating a folder specifically named "showshow". No matter what, if I make a folder with that name under s3fs, I get a folder where NO FILE can be written. All files placed in this folder simply end up being 0 bytes (glad I caught this!) It is not a Linux permissions issue. Check it out: user@server:~/s3fs-mountpoint$ mkdir showshow user@server:~/s3fs-mountpoint$ cd showshow user@server:~/s3fs-mountpoint/showshow$ touch test touch: closing `test': Bad file descriptor user@server:~/s3fs-mountpoint/showshow$ cd .. user@server:~/s3fs-mountpoint$ mkdir show user@server:~/s3fs-mountpoint$ cd show user@server:~/s3fs-mountpoint/show$ touch test user@server:~/s3fs-mountpoint/show$ ls test user@server:~/s3fs-mountpoint/show$ Weird eh? Why would this be? Thanks!!

kerem closed this issue

2026-03-04 01:42:29 +03:00

kerem commented

2026-03-04 01:42:30 +03:00

Author

Owner

@gaul commented on GitHub (Sep 10, 2015):

@Cat5TV This works for me. Can you retest this running s3fs with the -d -d -f -o f2 -o curldbg flags?

@gaul commented on GitHub (Sep 10, 2015): @Cat5TV This works for me. Can you retest this running s3fs with the `-d -d -f -o f2 -o curldbg` flags?

kerem commented

2026-03-04 01:42:30 +03:00

Author

Owner

@Cat5TV commented on GitHub (Sep 10, 2015):

Thanks @andrewgaul - I'm using fstab. What would you like me to try?

@Cat5TV commented on GitHub (Sep 10, 2015): Thanks @andrewgaul - I'm using fstab. What would you like me to try?

kerem commented

2026-03-04 01:42:30 +03:00

Author

Owner

@gaul commented on GitHub (Sep 10, 2015):

@Cat5TV You want mount without fstab for this -- we use the flags to dump debug output so we can further troubleshoot.

@gaul commented on GitHub (Sep 10, 2015): @Cat5TV You want mount without fstab for this -- we use the flags to dump debug output so we can further troubleshoot.

kerem commented

2026-03-04 01:42:30 +03:00

Author

Owner

@Cat5TV commented on GitHub (Sep 10, 2015):

Gives me "fuse: unknown option `f2' "

S3FS version 1.67

Yes, yes... I'll upgrade when I can replace the server, but it's operating on a live server.

Thanks!

@Cat5TV commented on GitHub (Sep 10, 2015): Gives me "fuse: unknown option `f2' " S3FS version 1.67 Yes, yes... I'll upgrade when I can replace the server, but it's operating on a live server. :) Thanks!

kerem commented

2026-03-04 01:42:30 +03:00

Author

Owner

@gaul commented on GitHub (Sep 10, 2015):

Sorry, 1.67 precedes my involvement in the project and later versions likely address your issue. I recommend upgrading to 1.79.

@gaul commented on GitHub (Sep 10, 2015): Sorry, 1.67 precedes my involvement in the project and later versions likely address your issue. I recommend upgrading to 1.79.

kerem commented

2026-03-04 01:42:30 +03:00

Author

Owner

@ggtakec commented on GitHub (Sep 13, 2015):

"f2" option was added after 1.67 because raw level debugging message on foreground mode.

The problem that the file size is zero, has occurred mainly such as communication timeout as a cause.
(Of course, it is not only it)
Please use the latest version that fixes a lot of problems.
We hope that it is the bes way to solve this issue.

Best Regards,

@ggtakec commented on GitHub (Sep 13, 2015): "f2" option was added after 1.67 because raw level debugging message on foreground mode. The problem that the file size is zero, has occurred mainly such as communication timeout as a cause. (Of course, it is not only it) Please use the latest version that fixes a lot of problems. We hope that it is the bes way to solve this issue. Best Regards,

kerem commented

2026-03-04 01:42:30 +03:00

Author

Owner

@Cat5TV commented on GitHub (Sep 14, 2015):

Thanks. Yes, I'll have to update the OS in order to do that. It was just a strange thing. I just went with a different folder name for now. :)

@Cat5TV commented on GitHub (Sep 14, 2015): Thanks. Yes, I'll have to update the OS in order to do that. It was just a strange thing. I just went with a different folder name for now. :)

kerem referenced this issue

2026-03-04 01:53:33 +03:00

[PR #134] [MERGED] Include Content-Type in complete MPU V2 signature #1356