[OpenAFS] VOS commands
I was wondering, what do the commands vos changeloc and vos convertROtoRW actually do? The vos help on these is rather scarce and openafs.org docs have nothing at all. Obviously new additions. Are they documented somewhere? Don't tell me in the defunct wiki. =) Luckily it's on its way back up... -Juha -- --- | Juha Jäykkä, [EMAIL PROTECTED]| | Laboratory of Theoretical Physics | | Department of Physics, University of Turku| | home: http://www.utu.fi/~juolja/ | --- pgpIxOxPyP877.pgp Description: PGP signature
Re: [OpenAFS] VOS commands
Juha Jäykkä wrote: I was wondering, what do the commands vos changeloc and vos convertROtoRW actually do? The vos help on these is rather scarce and openafs.org docs have nothing at all. Obviously new additions. Are they documented somewhere? Don't tell me in the defunct wiki. =) Luckily it's on its way back up... -Juha vos converRotoRW can be used if you have lost the partition where the RW-volume was but still have a RO-volume somewhere else. In this case you can convert the RO-volumes to the new RW-volume. This is much faster than a vos dump | vos restore because it only changes some fields in the volinfo-file and renames some files in /vicepx/AFSIDat//special This is part of a backup strategy: The mount points for our home directories are always made with the -rw option. We then have in the same partition a RO-volume and another one on a different server. The first RO-volume keeps the time needed for the reclone during vos release short and doesn't really consume much disk space because only changed files and some metadata files are duplicate. The remote RO-volumes are our real backup system. Even if you have lost a TB partition you can be back again in production after half an hour. Hartmut - Hartmut Reuter e-mail [EMAIL PROTECTED] phone +49-89-3299-1328 RZG (Rechenzentrum Garching) fax +49-89-3299-1301 Computing Center of the Max-Planck-Gesellschaft (MPG) and the Institut fuer Plasmaphysik (IPP) - ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] VOS commands
vos converRotoRW can be used if you have lost the partition where the RW-volume was but still have a RO-volume somewhere else. In this case you can convert the RO-volumes to the new RW-volume. This is much faster Ok, so that does exactly what the name suggests. Nice. The mount points for our home directories are always made with the -rw option. We then have in the same partition a RO-volume and another one on a different server. The first RO-volume keeps the time needed for the reclone during vos release short and doesn't really consume much disk space because only changed files and some metadata files are duplicate. We have the same setup, but it does not quite work as we supposed it would. We thought that anything accessing the RO version would automatically switch over to the other copy whenever to one it is currently accessing drops out of the network, but it does not seem to do so. Perhaps there is a misconfiguration somewhere? The situation is this: RW version of volume X on volume server A RO versions of X on servers A (on same partition as RW copy) and B Now users' $HOME is, of course, the RW version (/afs/blablabla/.username) and programs using $HOME will complain when A disappears. Those accessing the undotted version on the lost server should - to my understanding - move over to using server B in a few minutes after A is lost, but they do not. Why is this? Both volume servers are also db servers, plus there is an extra db server since the docs say ubik needs 2 servers to re-elect the master in case one is lost. [I do not actually know who's the master at the moment, but I suppose the third one is since it has the lowest IP.] The master runs upserver, the rest run upclient. That's about all relevant config info I think. -Juha -- --- | Juha Jäykkä, [EMAIL PROTECTED]| | Laboratory of Theoretical Physics | | Department of Physics, University of Turku| | home: http://www.utu.fi/~juolja/ | --- pgpbBASr630os.pgp Description: PGP signature
[OpenAFS] Tiger rc6 aklog and alternate service name
Hi all, I just installed 1.4.1-rc6 on my Tiger (10.4.4 on PowerPC PowerBook) and tried to get my AFS token using aklog. The result is: pathfinder:~ enrico$ aklog -d Authenticating to cell le.infn.it (server afs01.le.infn.it). We've deduced that we need to authenticate to realm LE.INFN.IT. Getting tickets: afs/[EMAIL PROTECTED] Kerberos error code returned by get_cred: -1765328324 aklog: Couldn't get le.infn.it AFS tickets: aklog: Generic error (see e-text) while getting AFS tickets It seems that this version of aklog is not able to switch to the alternate AFS service name in the form afs/@LE.INFN.IT, while the one coming with the openafs-1.4.0-8.SL (Scientific Linux) distribution works as I expect: [EMAIL PROTECTED] ~]$ aklog -d Authenticating to cell le.infn.it (server afs01.le.infn.it). We've deduced that we need to authenticate to realm LE.INFN.IT. Getting tickets: afs/[EMAIL PROTECTED] Principal not found, trying alternate service name: afs/@LE.INFN.IT About to resolve name enrico to id in cell le.infn.it. Id 20207 Set username to AFS ID 20207 Setting tokens. AFS ID 20207 / @ LE.INFN.IT Is it a bug or a feature? Ciao, Enrico begin:vcard fn:Enrico M. V. Fasanelli n:Fasanelli;Enrico M. V. org:I.N.F.N. - Sezione di Lecce;Servizio Calcolo Reti adr:Via Provinciale Lecce-Arnesano;;c/o Dipartimento di Fisica;Lecce;LE;73100;Italia email;internet:[EMAIL PROTECTED] tel;work:+39 0832 29 7442 tel;fax:+39 0832 29 7442 x-mozilla-html:FALSE version:2.1 end:vcard
Re: [OpenAFS] VOS commands
Juha Jäykkä wrote: The situation is this: RW version of volume X on volume server A RO versions of X on servers A (on same partition as RW copy) and B Now users' $HOME is, of course, the RW version (/afs/blablabla/.username) and programs using $HOME will complain when A disappears. Those accessing the undotted version on the lost server should - to my understanding - move over to using server B in a few minutes after A is lost, but they do not. Why is this? As soon as the client comes across a RW volume the path will be a RW path. Therefore the clients will not switch. Are you sure your clients are really using RO versions of the volume? Jeffrey Altman smime.p7s Description: S/MIME Cryptographic Signature
Re: [OpenAFS] Tiger rc6 aklog and alternate service name
Enrico M. V. Fasanelli wrote: Hi all, I just installed 1.4.1-rc6 on my Tiger (10.4.4 on PowerPC PowerBook) and tried to get my AFS token using aklog. The result is: pathfinder:~ enrico$ aklog -d Authenticating to cell le.infn.it (server afs01.le.infn.it). We've deduced that we need to authenticate to realm LE.INFN.IT. Getting tickets: afs/[EMAIL PROTECTED] Kerberos error code returned by get_cred: -1765328324 aklog: Couldn't get le.infn.it AFS tickets: aklog: Generic error (see e-text) while getting AFS tickets The KDC is returning a generic error not principal not found. Therefore, the aklog expects the KDC is simply broken and does not try a different principal name. If you can examine the exchange in a network monitor or review the KDC logs, what is the error text in the KRB-ERROR response? Jeffrey Altman smime.p7s Description: S/MIME Cryptographic Signature
Re: [OpenAFS] VOS commands
On Feb 7, 2006, at 2:58 PM, Juha Jäykkä wrote: ... We have the same setup, but it does not quite work as we supposed it would. We thought that anything accessing the RO version would automatically switch over to the other copy whenever to one it is currently accessing drops out of the network, but it does not seem to do so. Perhaps there is a misconfiguration somewhere? The situation is this: RW version of volume X on volume server A RO versions of X on servers A (on same partition as RW copy) and B Now users' $HOME is, of course, the RW version (/afs/ blablabla/.username) and programs using $HOME will complain when A disappears. Those accessing the undotted version on the lost server should - to my understanding - move over to using server B in a few minutes after A is lost, but they do not. Why is this? The client never switches from an RW volume to the RO copy. If you mounted the home dir with -rw, which you should and I'm sure you did, your client will never switch to any other replica. The replication is for read only data only, remember? ;-) Horst___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] OpenAFS + Kerb5
I'm a little confused as to the current state of the world. I'm not expecting any long answers. Grunts will do. I can dig further on my own after the grunts :) Kerb5 with OpenAFS: Is The Migration Kit necessary? Kerb5 with OpenAFS: Build MIT dist with fakeka? It wants kerb4 headers... I don't care about kerb4 whatsoever unless it's needed for OpenAFS. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] OpenAFS + Kerb5
I'm a little confused as to the current state of the world. I'm not expecting any long answers. Grunts will do. I can dig further on my own after the grunts :) Kerb5 with OpenAFS: Is The Migration Kit necessary? No (except maybe you should read the documentation if you want to understand what's going on). At least with 1.4.0, it includes aklog, and 1.4.1 includes asetkey which is all you need; technically you can get away without including asetkey, but it makes things a bit easier. Kerb5 with OpenAFS: Build MIT dist with fakeka? It wants kerb4 headers... I don't care about kerb4 whatsoever unless it's needed for OpenAFS. But MIT _does_ come with v4 headers, so that shouldn't be an issue. If you want klog to work, you need fakeka. If you don't care about klog and are just using aklog or an equivalant, then you don't need it. --Ken ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
RE: [OpenAFS] OpenAFS + Kerb5
There's a syntax change in Ken's writeup: des-cbc-crc should be des-cbc-crc:normal tedc -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Hornstein Sent: Tuesday, February 07, 2006 11:28 AM To: openafs-info@openafs.org Subject: Re: [OpenAFS] OpenAFS + Kerb5 I'm a little confused as to the current state of the world. I'm not expecting any long answers. Grunts will do. I can dig further on my own after the grunts :) Kerb5 with OpenAFS: Is The Migration Kit necessary? No (except maybe you should read the documentation if you want to understand what's going on). At least with 1.4.0, it includes aklog, and 1.4.1 includes asetkey which is all you need; technically you can get away without including asetkey, but it makes things a bit easier. Kerb5 with OpenAFS: Build MIT dist with fakeka? It wants kerb4 headers... I don't care about kerb4 whatsoever unless it's needed for OpenAFS. But MIT _does_ come with v4 headers, so that shouldn't be an issue. If you want klog to work, you need fakeka. If you don't care about klog and are just using aklog or an equivalant, then you don't need it. --Ken ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] afsd: Error -1 in basic initialization
I've compiled and installed successfully openafs-1.4.1-rc6 on a RedHat 7.3 with kernel-2.4.32 but when I run afsd I get: afsd: Error -1 in basic initialization. Running afsd -debug -verbose I get: afsd: My home cell is 'tenroses.com.ar' ParseCacheInfoFile: Opening cache info file '/usr/local/openafs//etc/openafs/cacheinfo'... ParseCacheInfoFile: Cache info file successfully parsed: cacheMountDir: '/afs' cacheBaseDir: '/usr/local/openafs/etc/cache' cacheBlocks: 10 afsd: cacheFiles autotuned to 3125 afsd: chunkSize autotuned to 18 afsd: dCacheSize autotuned to 2000 afsd: cacheStatEntries autotuned to 3000 afsd: 3125 inode_for_V entries at 0x8071ff8, 12500 bytes SScall(137, 28, 17)=-1 afsd: Forking rx listener daemon. afsd: Forking rx callback listener. afsd: Forking rxevent daemon. SScall(137, 28, 48)=-1 SScall(137, 28, 36)=-1 afsd: Error -1 in basic initialization. SScall(137, 28, 19)=-1 SScall(137, 28, 0)=-1 I have the kernel compiled with CONFIG_NOHIGHMEM set and I wonder if that is the problem. I've also tried openafs-1.2.13 but again the afs won't start. Both insmod /usr/local/openafs/lib/openafs/libafs-2.4.32.mp.o (openafs-1.4.1-rc6) and insmod /usr/vice/etc/modload/libafs-2.4.32.mp.o (openafs-1.2.13) leads to the same error: /usr/vice/etc/modload/libafs-2.4.32.mp.o: unresolved symbol kunmap_high /usr/vice/etc/modload/libafs-2.4.32.mp.o: unresolved symbol highmem_start_page /usr/vice/etc/modload/libafs-2.4.32.mp.o: unresolved symbol kmap_high /usr/vice/etc/modload/libafs-2.4.32.mp.o: Hint: You are trying to load a module without a GPL compatible license and it has unresolved symbols. Contact the module supplier for assistance, only they can help you. Thanks for your help. Maurizio Santini -- Maurizio Santini [EMAIL PROTECTED] ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] afsd: Error -1 in basic initialization
On Wed, 8 Feb 2006, Maurizio Santini wrote: I've compiled and installed successfully openafs-1.4.1-rc6 on a RedHat 7.3 with kernel-2.4.32 but when I run afsd I get: afsd: Error -1 in basic initialization. afsd isn't going to work until you get a working kernel module. I have the kernel compiled with CONFIG_NOHIGHMEM set and I wonder if that is the problem. I've also tried openafs-1.2.13 but again the afs won't start. Both insmod /usr/local/openafs/lib/openafs/libafs-2.4.32.mp.o (openafs-1.4.1-rc6) and insmod /usr/vice/etc/modload/libafs-2.4.32.mp.o (openafs-1.2.13) leads to the same error: /usr/vice/etc/modload/libafs-2.4.32.mp.o: unresolved symbol kunmap_high /usr/vice/etc/modload/libafs-2.4.32.mp.o: unresolved symbol highmem_start_page /usr/vice/etc/modload/libafs-2.4.32.mp.o: unresolved symbol kmap_high /usr/vice/etc/modload/libafs-2.4.32.mp.o: That suggests somehow your kernel headers that AFS was compiled against don't match the kernel you're running. Compile a module against the headers from the running kernel, and try again. Derrick ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
