Next: So What Should I Worry About? Previous: What Did All That Mean? Up: Lost Contact With File Server

So What Did I Lose?

The first thing you want to do will probably be to find out which locker you've just lost. Suppose you have just received the message:

afs: Lost contact with file server 18.70.0.210 in cell athena.mit.edu

The number 18.70.0.210 is the internet address of the machine; the command hostinfo will tell you what the name of the machine is. So typing hostinfo 18.70.0.210 will give you this:

Desired host: 18.70.0.210 Official name: ROSEBUD.MIT.EDU Host address: 18.70.0.210

This tells you that the name of the machine is rosebud. If you want to know whether a particular locker is on that server, you can use the command lookup (in the consult locker). Thus lookup sorokin will return:

Filesystem sorokin (AFS) is located on:

ROSEMARY.MIT.EDU (read-write)

which says that sorokin's homedir is still accessible. lookup sipb will return:

Filesystem (AFS) is located on:

ROSEBUD.MIT.EDU (read-write) ROSEBUD.MIT.EDU (read-only) RONALD-ANN.MIT.EDU (read-only, alternate)

This tells you that sipb is located on rosebud. Handily, there is another file server containing the same data (ronald-ann), and so you probably shouldn't be worried. However, you may want to look at all the filesystems you have attached. The command for this (also in the consult locker) is wherefs. It will give you something like this:

sorokin : AFS filesystem on host ROSEMARY.MIT.EDU sipb : AFS filesystem on host ROSEBUD.MIT.EDU gnu : AFS filesystem on host ARTEMIS.MIT.EDU consult : AFS filesystem on host CHICKADEE.MIT.EDU graphics : AFS filesystem on host KITE.MIT.EDU

There may be lockers listed that you don't recognize. The reason for this is that when you attach a locker, it is connected to the workstation. Therefore, a locker attached by the previous user may show up in your listing. You can ignore it.