[PR #579] [MERGED] Added notsup_compat_dir option #1555

New issue

Closed

opened 2026-03-04 02:01:01 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 02:01:01 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/579
Author: @ggtakec
Created: 5/5/2017
Status: ✅ Merged
Merged: 5/5/2017
Merged by: @ggtakec

Base: master ← Head: master

📝 Commits (1)

3ac39d6 Added notsup_compat_dir option

📊 Changes

3 files changed (+50 additions, -8 deletions)

View changed files

📝 doc/man/s3fs.1 (+11 -0)
📝 src/s3fs.cpp (+21 -8)
📝 src/s3fs_util.cpp (+18 -0)

📄 Description

Relevant Issue (if applicable)

#571

Details

As a default, s3fs supports objects of the directory type as much as possible and recognizes them as directories.
Objects that can be recognized as directory objects are "dir/", "dir", "dir_$folder$", and there is a file object that does not have a directory object but contains that directory path.

s3fs needs redundant communication to support all these directory types.
The object as the directory created by s3fs is "dir/".
By restricting s3fs to recognize only "dir/" as a directory, communication traffic can be reduced.
This option is used to give this restriction to s3fs.
However, if there is a directory object other than "dir/" in the bucket, specifying this option is not recommended.
s3fs may not be able to recognize the object correctly if an object created by s3fs exists in the bucket.
Please use it when the directory in the bucket is only "dir/" object.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/579 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 5/5/2017 **Status:** ✅ Merged **Merged:** 5/5/2017 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`3ac39d6`](https://github.com/s3fs-fuse/s3fs-fuse/commit/3ac39d61f84134bb4dbc60b203be154cf56eae1b) Added notsup_compat_dir option ### 📊 Changes **3 files changed** (+50 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `doc/man/s3fs.1` (+11 -0) 📝 `src/s3fs.cpp` (+21 -8) 📝 `src/s3fs_util.cpp` (+18 -0) </details> ### 📄 Description #### Relevant Issue (if applicable) #571 #### Details As a default, s3fs supports objects of the directory type as much as possible and recognizes them as directories. Objects that can be recognized as directory objects are "dir/", "dir", "dir_$folder$", and there is a file object that does not have a directory object but contains that directory path. s3fs needs redundant communication to support all these directory types. The object as the directory created by s3fs is "dir/". By restricting s3fs to recognize only "dir/" as a directory, communication traffic can be reduced. This option is used to give this restriction to s3fs. However, if there is a directory object other than "dir/" in the bucket, specifying this option is **not recommended**. s3fs may not be able to recognize the object correctly if an object created by s3fs exists in the bucket. Please use it when the directory in the bucket is only "dir/" object. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>