I started off my s3fs journey using s3fs_migrate to move my files over because we had issues with advagg and couldn't use public takeover. That said, s3fs_migrate stores files on s3 in the s3fs-public folder on s3. We were investigating why some image styles were getting 404s when I found out that if you upload a file to the s3fs-public (or s3fs-private) folders in s3, and then you run drush s3fs-rc, that it will rewrite the uri's in the s3fs_file table as either public:// or private:// based on where you stored your stuff. Obviously the file_managed table had s3://s3fs-public/path/to/image... and public still equated to the disk where those files were not stored... Addtionally, s3fs couldn't find those uris in the s3fs_file table, so... it just gave up and said the file didn't exist. Attaching patch soon for check to make sure the use_s3_for_* options are respected in metadata refresh.
Closed: outdated
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Drupal 7 end-of-life triage:
Drupal 7 will reach end of life on January 5th.
The 7.x branches of S3FS do not have any additional planned releases.
The requests in this issue do not appear to exist in the 8.x-3.x and newer branches.