AFP Problems?

AFP Problems?

Posted by: tonycpsu
Posted on: 2005-10-27 19:53:00

I'm not sure how "officially" AFP is supported, but I figured I'd ask if any other Mac geeks are able to successfully use AFP. I can mount my share fine, but I can't seem to write anything. From a terminal, when I try to create a new file, I get an "invalid argument" error. If I try to create a file from the Finder (e.g. copying a file) I get "Error -50". I didn't find anything about this in my forum search so I figured I'd ask here. Thanks for any and all help.

Re: AFP Problems?

Posted by: matnet
Posted on: 2005-12-19 12:18:00

If you look at the bottom of your Finder mount... does it say Zero KB available? If so the AFP share is out of space. This does not mean the whole server is, just how much space was alotted to share with Netatalk/AFP, and probably listed in it's config file. I had been using it for quite some time on a number of my accounts (and still do) but this happed to my MAIN server. They (support) have fixed problems related to AFP before... but not for this case... I fear it has to do with the person you get on tech support- some will go ahead and deal with the issue, some will just pull the 'unsupported' service, cop out sentence. A real bummer as this is an incredibly useful service. It was the only way I could use a shared Quickbooks file with my partners. Now I may have to take a drastic step... after being jerked around, I am thinking of moving myself and my 60 + clients to a rackspace server. Maybe not though, I love most of Dreamhost. I love the sometimes cutting edge services they offer, I hate it, when they cannot get it together, like in this case (Not that AFP is cutting edge...) Now subversion and Trac ,and collab... well let's hope the best for these....

Artist, Scholar, Gentleman ... Technophile

Re: AFP Problems?

Posted by: tonycpsu
Posted on: 2005-12-19 12:36:00

Actually, this problem went away for me right after upgrading to OS X 10.4.3. I don't know if the two events are/were related, but I haven't had any AFP problems since updating to 10.4.3.

Re: AFP Problems?

Posted by: matnet
Posted on: 2005-12-19 13:04:00

I'm quite glad for you...

For me my 5 other servers contain plenty of space, way up there in 'gigabyte land', however my one plan, (unfortunately, my oldest and central plan) sits on a server, or server group named dib, and AFP shows out of space, and no matter how many files I destroy to make room, it still remains out of space on AFP... I cannot write to it, or copy to it, or open files on it... but I can on all my other servers, which, ironically, I do not need AFP on!

Bummer.
Thanks for the reply though, it really is cool that this is 'sort of' available.

PS. These are the last support responses I recieved from Dreamhost staff in order- old to new (thought this would help people in the forum with similar problems.):
October 26th, 05 -Hello,
I have been personally working on getting afp / netatalk working again. The package that comes with Debian Sarge is broken and I have been looking into ways of getting it working again with no luck. I apologize for the trouble and there is no ETA on when or if this will be available again. Sorry I could not be of more help at this time.
Thanks!
Jordan
(Note from me, Mat: Notice, Jordan did not give me the "unsupported" line...)

Re: me too! AFP Problems?

Posted by: dvb
Posted on: 2006-09-02 16:22:00

YIKES. I have been having the same problem. I can mount AFP to see my whole account, but the finder says Zero KB Available.

Now, here's the kicker: I created another use account (they're both on gage), created a SYMBOLIC LINK to the first account, and from the second account I can AFP in and it works great! 186.1 GB available. That's more like it.

So this story about "limited AFP Space" is just wrong. It's some kind of account setting thing, or some kind of Mac OS X cached-badness-cookielike thing.

So I'm all mad but have a workaround and maybe these datum can be evaluated by someone of cooler disposition than myself.

Cheers!

Tags: askforum searchinvalid argumentsuccessfullyhelpnew file