[OpenAFS] Can't mount AFS

[Jason Frisch]

I think I have it!

1. # */usr/afs/bin/vos create* <machine name> <partition name> *root.cell*
2. # */usr/afs/bin/fs mkmount /afs/*cellname *root.cell*
3. # */usr/afs/bin/fs setacl /afs/*cellname *system:anyuser rl

I think I missed this bit.

# vos create -server localhost -partition /vicepa -name root.cell
vsu_ClientInit: Could not get afs tokens, running unauthenticated.

Could not get an Id for volume root.cell
   VLDB: no permission access for call
VLDB: no permission access for call
Error in vos create command.
VLDB: no permission access for call
---------------------------------------------------------
Probably inforrect arguments...


[root@backup vicepa]# fs mkmount -dir /viceafs -cell tsukaeru.net -vol 
root.cell
fs: mount points must be created within the AFS file system

Do I need to create /afs/tsukaeru.net manually? I probably just have he
options wrong again :-(


*3. # */usr/afs/bin/fs setacl /afs/*cellname *system:anyuser rl

Hmm. I am not sure what is what in this one.. Is system:anyuser the
acl? what is r1..the id?

Sorry for all the dumb questions. If only someone would update the
docs hey!

Jason

**
*Horst Birthelmer wrote:

>
> On Oct 14, 2005, at 12:17 PM, Jason Frisch wrote:
>
>> BTW, what machine is that? Kernel Version, Distribution?
>> [root@backup etc]# uname -a
>> Linux backup.tsukaeru.net 2.4.21-37.EL #1 Wed Sep 28 14:14:23 EDT  
>> 2005 i686 i686 i386 GNU/Linux
>>
>> Is the client working with disk cache?
>>
>> I believe so. My afs file in /etc/sysconfig/afs has cache setup.
>>
>
> <quote>
>
>> SScall(137, 28, 6)=0 afsd: Sweeping workstation's AFS cache directory.
>> afsd: Using memory cache, not swept
>
> <\quote>
>
> from your client startup log, it's set to use memcache. But it's  
> unlikely that that's your problem.
>
>> [root@backup etc]# ps -ef | grep afs
>> root     10034     1  0 09:41 ?        00:00:00 /usr/afs/bin/bosserver
>> root     10039 10034  0 09:41 ?        00:00:00 /usr/afs/bin/kaserver
>> root     10040 10034  0 09:41 ?        00:00:00 /usr/afs/bin/buserver
>> root     10041 10034  0 09:41 ?        00:00:00 /usr/afs/bin/ptserver
>> root     10042 10034  0 09:41 ?        00:00:00 /usr/afs/bin/vlserver
>> root     10044 10034  0 09:41 ?        00:00:00 /usr/afs/bin/ 
>> upserver -crypt /usr/afs/etc -clear /us
>> r/afs/bin
>> root     10059     1  0 09:41 ?        00:00:00 [afs_rxlistener]
>> root     10061     1  0 09:41 ?        00:00:00 [afs_callback]
>> root     10063     1  0 09:41 ?        00:00:00 [afs_rxevent]
>> root     10065     1  0 09:41 ?        00:00:00 [afsd]
>> root     10067     1  0 09:41 ?        00:00:00 [afs_checkserver]
>> root     10069     1  0 09:41 ?        00:00:00 [afs_background]
>> root     10071     1  0 09:41 ?        00:00:00 [afs_background]
>> root     10073     1  0 09:41 ?        00:00:00 [afs_background]
>> root     10075     1  0 09:41 ?        00:00:00 [afs_background]
>> root     10077     1  0 09:41 ?        00:00:00 [afs_background]
>> root     10079     1  0 09:41 ?        00:00:00 [afs_background]
>> root     10081     1  0 09:41 ?        00:00:00 [afs_cachetrim]
>> root     10084 10034  0 09:41 ?        00:00:00 /usr/afs/bin/ fileserver
>> root     10085 10034  0 09:41 ?        00:00:00 /usr/afs/bin/volserver
>> root     11966  9969  0 19:10 pts/0    00:00:00 grep afs
>>
>> Looks like it is running.  I don't have any other clients yet, and  this
>> server has both server and client.
>>
> You did the installation as stated in the documentation, right?
>
> What does "vos listvl" say? Did you create the volumes root.afs and  
> root.cell?
> I'm running out of ideas what could cause an EINVAL during /afs mount.
>
> Horst
>