starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 21:35:58 +03:00

[GH-ISSUE #191] Permissons of mounted bucket don't allow reading #108

New issue

Closed

opened 2026-03-04 01:42:11 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @bitwombat on GitHub (May 28, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/191

Using Ubuntu 14.04 LTS, I can mount but see this:

$ ll mountpnt
total 512
d--------- 1 root 0 Oct 30  2014 wordpress_backups

I'm afraid to chmod that... is there a good reason nobody can read that dir?

Originally created by @bitwombat on GitHub (May 28, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/191 Using Ubuntu 14.04 LTS, I can mount but see this: ``` $ ll mountpnt total 512 d--------- 1 root 0 Oct 30 2014 wordpress_backups ``` I'm afraid to chmod that... is there a good reason nobody can read that dir?

kerem closed this issue

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

kerem commented

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

Author

Owner

@kahing commented on GitHub (May 28, 2015):

Was it a directory that was written through s3fs or through some other applications? s3fs relies on its own metadata to store the permissions, without those metadata it's expected to show what you see here

@kahing commented on GitHub (May 28, 2015): Was it a directory that was written through s3fs or through some other applications? s3fs relies on its own metadata to store the permissions, without those metadata it's expected to show what you see here

kerem commented

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

Author

Owner

@bitwombat commented on GitHub (May 28, 2015):

It's an existing bucket, so it was created/written via the web interface.

What do I do in that use case?

@bitwombat commented on GitHub (May 28, 2015): It's an existing bucket, so it was created/written via the web interface. What do I do in that use case?

kerem commented

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

Author

Owner

@bitwombat commented on GitHub (Jun 9, 2015):

Put another way, can I initialise the metadata from an existing bucket?

@bitwombat commented on GitHub (Jun 9, 2015): Put another way, can I initialise the metadata from an existing bucket?

kerem commented

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

Author

Owner

@kahing commented on GitHub (Jun 9, 2015):

Could you try chmod'ing the files manually?

@kahing commented on GitHub (Jun 9, 2015): Could you try chmod'ing the files manually?

kerem commented

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

Author

Owner

@ertrzyiks commented on GitHub (Jun 30, 2015):

That happens when you upload files from website. S3 bucket store permissions in metadata field called x-amz-meta-mode and default value is 0000. Once you set chmod manually on mounted folder, s3fs will update that field and your chmod will be remembered for next time you mount your bucket.

@ertrzyiks commented on GitHub (Jun 30, 2015): That happens when you upload files from website. S3 bucket store permissions in metadata field called `x-amz-meta-mode` and default value is 0000. Once you set chmod manually on mounted folder, s3fs will update that field and your chmod will be remembered for next time you mount your bucket.

kerem commented

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

Author

Owner

@bitwombat commented on GitHub (Jun 30, 2015):

Ah, beauty. Thanks ertrzyiks.

@bitwombat commented on GitHub (Jun 30, 2015): Ah, beauty. Thanks ertrzyiks.