[GH-ISSUE #455] Set storage type per folder #246

New issue

Closed

opened 2026-03-04 01:43:38 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:43:38 +03:00

Owner

Originally created by @cowmix88 on GitHub (Jul 27, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/455

Feature Request: It would be nice to be able to override the default storage type per directory.

For example:
/s3 - standard (default)
/s3/folder1 - redundant (override default)
/s3/folder1/folder3 - standard (override redundant)
/s3/folder2 - standard ia (override default)

Maybe this could be done using the key metadata?

I guess one way that I can currently achieve this is to create multiple mounts with the nonempty option to override the existing default storage type?

Originally created by @cowmix88 on GitHub (Jul 27, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/455 Feature Request: It would be nice to be able to override the default storage type per directory. For example: /s3 - standard (default) /s3/folder1 - redundant (override default) /s3/folder1/folder3 - standard (override redundant) /s3/folder2 - standard ia (override default) Maybe this could be done using the key metadata? I guess one way that I can currently achieve this is to create multiple mounts with the nonempty option to override the existing default storage type?

kerem

2026-03-04 01:43:38 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-04 01:43:39 +03:00

Author

Owner

@ggtakec commented on GitHub (Sep 19, 2016):

@cowmix88
Current s3fs can not be set the strage class to each folder.
I think this requirement is needed to consider at the future, then please wait.

The following is a proposed workaround:
You can mount on two mount point for same S3 bucket by s3fs.
One is with normal strage class, the other is with redundancy class.
And you create the directory to combine these into one, and you link sub directories as symbolic to the directories in these mountpoint.
Then I think that it is possible that you want to your realization.

Thanks in advance for your assistance.

@ggtakec commented on GitHub (Sep 19, 2016): @cowmix88 Current s3fs can not be set the strage class to each folder. I think this requirement is needed to consider at the future, then please wait. The following is a proposed workaround: You can mount on two mount point for same S3 bucket by s3fs. One is with normal strage class, the other is with redundancy class. And you create the directory to combine these into one, and you link sub directories as symbolic to the directories in these mountpoint. Then I think that it is possible that you want to your realization. Thanks in advance for your assistance.

kerem commented

2026-03-04 01:43:39 +03:00

Author

Owner

@gaul commented on GitHub (Feb 2, 2019):

@cowmix88 Could you accomplish this by using an S3 lifecycle policy applied to given prefixes? This seems outside the scope of s3fs.

@gaul commented on GitHub (Feb 2, 2019): @cowmix88 Could you accomplish this by using an S3 lifecycle policy applied to given prefixes? This seems outside the scope of s3fs.

kerem commented

2026-03-04 01:43:39 +03:00

Author

Owner

@gaul commented on GitHub (Feb 3, 2020):

Closing due to inactivity. Please reopen if symptoms persist.

@gaul commented on GitHub (Feb 3, 2020): Closing due to inactivity. Please reopen if symptoms persist.

kerem referenced this issue

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

[PR #246] [MERGED] Unlock during early return in TruncateCache #1420