Hi, On Mon, Jan 30, 2012 at 14:09, Andrew Deason <[email protected]> wrote: > On Mon, 30 Jan 2012 13:51:05 -0500 > Dan Scott <[email protected]> wrote: > >> One of my openafs-1.6.1-0.pre1 servers is having problems. >> >> It's showing the following in its logs: >> >> Volser: GetVolInfo: Could not attach volume (/vicepa:) error=101 > > If that is the exact error message, something is requesting volume info > for... hm, a volume with the empty string for its header filename. > > That is odd, but that is only an error generated for something like a > 'vos examine' or 'vos listvol' etc; it should not indicate that a volume > is completely unavailable.
Sorry, I removed the volume IDs - force of habit. There are real volume IDs in the messages. >> and the volumes are not accessible. > > How specifically are they not accessible? How are you trying to access > them, and what error do you get? If you are trying to access files in > the volume from a client, the FileLog may say something about the > volume. All of the volumes under a particular mount point give: djscott@pc35:~$ ls /afs/example.com/volume ls: cannot access /afs/example.com/volume: No such device Other volumes on other servers are fine. I just ran the salvager which fixed a load of problems, but still no luck. Thanks, Dan _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
