Loading Profile...
Mac problem - S3 - privileges and not being able to add anything
Hi there, I've connected ok to S3 but have no privileges to create a folder, and it won't except anything I drag and drop.
Any thoughts?
Thanks!
Any thoughts?
Thanks!
I’m frustrated
5
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solutions from the company
-
You can actually create buckets with ExpanDrive now, it just requires that you use the Terminal. If your S3 account is mounted as "Amazon S3", you can go to the Terminal and write:
% cd "/Volumes/Amazon S3"
% mkdir "MyNewBucketName"
There are two basic reasons why the Finder's default "Untitled Folder" does not work: First, because spaces are not allowed by S3 in bucket names; and second, because bucket names must be globally unique, and so even if that name were legal, you would get a conflict everytime someone else tried to create it.
As Jeff said, we're hoping to provide a more user-friendly interface for bucket creation in the future, but in the meantime, you can do it, as I described here.
3 people say
this solves the problem
-
Just pushed out 2.0.1 which fixes all sorts of things
http://blog.expandrive.com/2009/05/01...
Thanks for the patience!
I’m happy
The company says
this solves the problem
-
Inappropriate?You have to remember about S3 is the default root contains buckets for all users. You don't have a special bucket for all you stuff. As a result I can make a folder called 'untitled folder' if you already have that created.
I received this from Jon via email yesterday:
Bucket creation is a little tricky, and we haven’t added support for it yet. Basically, when you create a new folder in the Finder, it makes a folder called "untitled folder", and then lets you rename it. Obvious we can’t create a bucket named "untitled folder" on S3 every time someone creates a bucket, so we need to come up with some way to catch directory/bucket creation and handle them in some other way. We’re thinking that when you try to make a directory/bucket that we’ll open a window in the ExpanDrive interface to prompt you for the bucket name, rather than letting the Finder try to do it. We should get this going some time soon.
I think think of a few ways I would like see Exandrive handle bucket creation without user interaction... but a simple "fix" for now. Use cyber duck, a free little program, log into your account and create a bucket. I used "myosxuid_expandrive" then set the remote path to that.
I’m giving ideas.
-
Inappropriate?Jon -
My guess is that you're trying to drop a file into the "root" of the s3 drive. You might first need to create an S3 bucket [using a 3rd party program], to which you can then add info.
We'll be adding support to create buckets soon, just not there yet
-Jeff -
Inappropriate?You can actually create buckets with ExpanDrive now, it just requires that you use the Terminal. If your S3 account is mounted as "Amazon S3", you can go to the Terminal and write:
% cd "/Volumes/Amazon S3"
% mkdir "MyNewBucketName"
There are two basic reasons why the Finder's default "Untitled Folder" does not work: First, because spaces are not allowed by S3 in bucket names; and second, because bucket names must be globally unique, and so even if that name were legal, you would get a conflict everytime someone else tried to create it.
As Jeff said, we're hoping to provide a more user-friendly interface for bucket creation in the future, but in the meantime, you can do it, as I described here.
3 people say
this solves the problem
-
Inappropriate?Thanks for the comments and help guys. Still no joy I'm afraid. I did the terminal commands and just got this:
Jons-MacPro:~ jonmoss$ % cd "/Volumes/S3"
-bash: fg: %: no such job
Jons-MacPro:~ jonmoss$
Jons-MacPro:~ jonmoss$ % mkdir "Jon's S3"
-bash: fg: %: no such job
Jons-MacPro:~ jonmoss$
Any help, much appreciated.
I’m frustrated
1 Comment Add a comment
This solves the problem
-
I'm sorry, I was unclear in my instructions: The "%" that I wrote above was meant to represent the command prompt, and should not be typed as part of the command itself. Could you please try the commands again, but omitting the "%" at the beginning? -
Inappropriate?Many thanks! Just tried again and has not done anything :-(
Hmmm... I'm not a terminal expert, far from it I'm afraid!
When I get the S3 mounted I have 2 folders with long names. I could actually make a folder in one of them, and allowed me to upload a file, but I could then not see it.
I so want this to work as dying to have an easy way to back up to S3 :-(
I’m frustrated
1 Comment Add a comment
This solves the problem
-
Hi, Jon,
If you mount your S3 drive and see the two long-named folders, you should be able to see the same names if you run the command "ls /Volumes/S3" (without the quotes) in the Terminal. If you're not getting that, please feel free to drop us an e-mail at <support@expandrive.com>, and we'll do our best to help you troubleshoot. -
Inappropriate?Used Transmit to create a bucket, everything works now.
Saying that you support S3 without being able to create a bucket... I'm not sure how I feel about that.
Expandrive was my first experience with S3 (and vice versa). I'm not sure what to make of it since its S3 support isn't quite useful without another app (I used Transmit) to make the bucket.
Seems to work OK otherwise.
I’m left with a bad first impression
-
Inappropriate?Actually, I take that back... Creating folders worked, uploading files didn't. File dropped into the folder, never appeared on S3. I'll check back when 2.1 is out :(
I’m sorry to leave
-
Inappropriate?I installed Expandrive 2 yesterday on my Mac and have the same problem. Very frustrating. I was looking forward to a better way of uploading files to S3.
I’m frustrated
-
Inappropriate?So, have we got any definitive solution here or not? I am frankly really brassed off that the S3 feature is advertised, and promised, and it is quite clearly not ready for general use.
Don't get me wrong, if it worked simply, I would be talking to a lot of people about this / blogging about it. Right now though, I just tell people not to bother. That is sad, as it looks like a great product. If it worked for S3
I’m right, proper brassed off.
-
Inappropriate?Hey Jon,
I recommend using another application to create the bucket (e.g. Transmit, which has full S3 support) and then using Expandrive to store files there.
Unfortunately even this did not work for me as files dropped into the bucket I created with Transmit never appeared. Perhaps I'm doing something wrong? I chose to give up, just using Transmit until S3 support matures.
Best to look elsewhere I'm afraid - definite growing pains here.
I’m wishing it worked well
-
Inappropriate?Hi Rob, I'll give it a go in Transmit over the weekend and see how we go! (not holding out much hope though).
I’m sad
-
Inappropriate?We've got a fix coming today - thanks for the patience guys.
-
Inappropriate?ok...
use the terminal autocomplete (hit tab once or twice)
for example, my S3 bucket is named: mybuckets
in terminal
cd /Volumes/
hit tab twice and find the nickname of your mounted server.
type in the first few letters (2 or 3 usually works) and hit tab.
code continued:
cd /Volumes/mybuckets
then hit return.
Note: if you have a space in your nickname, terminal will escape it.
So, if mybucket was name 'My Buckets' it will return:
cd /Volumes/My\ Buckets/
hitting tab will help complete this with escaped characters.
and then mkdir will work the same
- eric
I’m happy
-
Inappropriate?Just pushed out 2.0.1 which fixes all sorts of things
http://blog.expandrive.com/2009/05/01...
Thanks for the patience!
I’m happy
The company says
this solves the problem
EMPLOYEE
EMPLOYEE
