YAS3FS (Yet Another S3-backed File System) is a Filesystem in Userspace (FUSE) interface to Amazon S3. It was inspired by s3fs but rewritten from scratch to implement a distributed cache synchronized by Amazon SNS notifications. A web console is provided to easily monitor the nodes of a cluster.
In https://github.com/danilop/yas3fs/commit/32fe47282a49f6e5085d9e02541b1be5a58bd770 a quite significant change was made to the FUSE setup call. This setting apparently means that chmod on yas3fs mounted directories and files now returns EPERM instead of failing silently. This change can now be undone with the --no-default-permissions switch but this is not documented anywhere, I had to discover this by reading the source.
In my case, this is important for my application as it attempts to chmod and throws an error when the EPERM is returned, even though the permissions are sufficient for the application to work with the previous silent failure. This is strictly my fault for running master instead of a tagged release (I was on master because I also need other fixes that are not present in 2.3.5) and I figure that this may affect other users of yas3fs if/when a tagged release of 2.4.0 is made if it is not documented first.
In https://github.com/danilop/yas3fs/commit/32fe47282a49f6e5085d9e02541b1be5a58bd770 a quite significant change was made to the FUSE setup call. This setting apparently means that
chmodon yas3fs mounted directories and files now returns EPERM instead of failing silently. This change can now be undone with the--no-default-permissionsswitch but this is not documented anywhere, I had to discover this by reading the source.In my case, this is important for my application as it attempts to chmod and throws an error when the EPERM is returned, even though the permissions are sufficient for the application to work with the previous silent failure. This is strictly my fault for running master instead of a tagged release (I was on master because I also need other fixes that are not present in 2.3.5) and I figure that this may affect other users of yas3fs if/when a tagged release of 2.4.0 is made if it is not documented first.