Hi Michelle, The generation of keys was something we had to do on the bucket. That’s not something you have to do on your end. S3fs requires that the top-level folders have to be represented as objects in the bucket. The lack of those keys was initially preventing mounting.
You may want to enable debugging in s3fs to get more detailed information about the issue you’re seeing. Here’s the command I’m using on my end to mount, where 1000 is the UID and GID of my local user on my Linux VM. I’ve got the debugging flags enabled in this example (“-d -d -f”): s3fs -o allow_other,uid=1000,gid=1000,umask=227,use_cache=/tmp,ro hcp-openaccess-temp:/HCP_1200 /mnt/s3/HCP_1200 -d -d -f Regards, Mike From: [email protected] <[email protected]> On Behalf Of Michelle Chiu Sent: Tuesday, August 14, 2018 2:07 PM To: [email protected] Subject: Re: [HCP-Users] mounting temp bucket Hello all, I've been having issues mounting the HCP_1200 folder since the migration - I was wondering how you'd generate keys for the top-level folders, as Mike has recommended, and how that is different from the access key IDs I place into my .passwd-s3fs file? Thank you! Best, Michelle _______________________________________________ HCP-Users mailing list [email protected]<mailto:[email protected]> http://lists.humanconnectome.org/mailman/listinfo/hcp-users ________________________________ The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail. _______________________________________________ HCP-Users mailing list [email protected] http://lists.humanconnectome.org/mailman/listinfo/hcp-users
