[OpenAFS] Problems on AFS Unix clients after AFS fileserver moves

Rich Sudlow rich@nd.edu
Tue, 09 Aug 2005 11:58:24 -0500


rogbazan wrote:

> That has been our solution....try it!

Unfortunately that didn't work.

Thanks

Rich

> 
> 
> On 8/9/05, Derrick J Brashear <shadow@dementia.org> wrote:
> 
>>On Tue, 9 Aug 2005, Rich Sudlow wrote:
>>
>>
>>>[root@xeon109 root]# fs checkservers
>>>These servers unavailable due to network or server problems:
>>>reno.helios.nd.edu.
>>
>>That's fine.
>>
>>
>>>[root@xeon109 root]# cmdebug reno.helios.nd.edu -long
>>>cmdebug: error checking locks: server or network not responding
>>
>>If reno is a server, this is uninteresting, as cmdebug is for checking
>>client state.
>>
>>
>>>[root@xeon109 root]#  vos listvldb -server reno.helios.nd.edu
>>>VLDB entries for server reno.helios.nd.edu
>>>
>>>Total entries: 0
>>
>>ok.
>>
>>
>>>This is a linux 2.4 client and I don't have kdump - have also had these
>>>problems on sun4x_58 clients too.
>>
>>well, what's the problem? none of the information above points to a
>>problem accessing files, only that a server which is down is showing down
>>
>>_______________________________________________
>>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


-- 
Rich Sudlow
University of Notre Dame
Office of Information Technologies
321 Information Technologies Center
PO Box 539
Notre Dame, IN 46556-0539

(574) 631-7258 office phone
(574) 631-9283 office fax