[OpenAFS] cache problems in cluster environment

[Thomas Sesselmann]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC147E1D87D29F6E982D8C6AB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,

Derrick J Brashear schrieb:
> On Tue, 21 Aug 2007, Thomas Sesselmann wrote:
>> we are using OpenAFS in a cluster-environment.
>> Now we have about 100 Linux-Clients (Ubuntu 6.06)
>> with OpenAFS 1.4.1-2 (system-default).
>=20
> callback breaks being dropped, so the client isn't refetching. what on
> your network is either filtering or expiring port mappings, and can you=

> fix it?

As i know, we didn't use NAT or a FW between the clients and the AFS-Serv=
ers.


I found the potential issue, i think.
The UUID for the client (cache manager) isn't calculated:

'cmdebug <client> -addr' shows:
UUID: 00000000-0000-0000-00-00-000000000000
Host interfaces:
Capabilities:
Error Translation


The clients have a bonding of two interfaces:

ifconfig
bond0     Link encap:Ethernet  HWaddr 00:E0:81:48:23:52
          inet addr:10.162.8.199  Bcast:10.162.255.255  Mask:255.255.0.0
          inet6 addr: fe80::2e0:81ff:fe48:2352/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:3358681 errors:0 dropped:0 overruns:0 frame:0
          TX packets:738705 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:234868766 (223.9 MiB)  TX bytes:72026030 (68.6 MiB)

eth1      Link encap:Ethernet  HWaddr 00:E0:81:48:23:52
          inet6 addr: fe80::2e0:81ff:fe48:2352/64 Scope:Link
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:3040255 errors:0 dropped:0 overruns:0 frame:0
          TX packets:385736 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:209332396 (199.6 MiB)  TX bytes:36951684 (35.2 MiB)
          Interrupt:177

eth2      Link encap:Ethernet  HWaddr 00:E0:81:48:23:52
          inet6 addr: fe80::2e0:81ff:fe48:2352/64 Scope:Link
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:318426 errors:0 dropped:0 overruns:0 frame:0
          TX packets:352969 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:25536370 (24.3 MiB)  TX bytes:35074346 (33.4 MiB)
          Interrupt:185

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:69936 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69936 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10637114 (10.1 MiB)  TX bytes:10637114 (10.1 MiB)


Is this the problem?
How is the UUID calculated?


thanks and best regards

Thomas Sesselmann

--=20
Dipl.-Inf. Thomas Sesselmann         __O
Kirchhoff-Institut f=FCr Physik      _\-<,
Universit=E4t Heidelberg           _(_)/(_)_
INF227 / D-69120 Heidelberg
Tel.:   +49/6221/54-9132
E-Mail: Thomas.Sesselmann@kip.uni-heidelberg.de
gpg-key: 0x9392E54B  or finger -l tsesselm@ix.urz.uni-heidelberg.de


--------------enigC147E1D87D29F6E982D8C6AB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGy/YlEQVslJOS5UsRCr6fAKCknVNG6YGQcYjwgNpWvdKoFy2mQgCfXJyi
z6w2IFkQEvXSx4a30IYOGLM=
=6U9d
-----END PGP SIGNATURE-----

--------------enigC147E1D87D29F6E982D8C6AB--