[OpenAFS] Upgrading Transarc servers

I think this is the case, but wanted to verify. When upgrading from Transarc fileserver binaries to OpenAFS, there are no disk format changes? Just swap out the binaries and go. Correct? Also, there is no need to change from the Transarc fsck program. Correct? Thanks! Kevin

Re: [OpenAFS] Upgrading Transarc servers

Depends on the architectures your fileservers are running on. For Linux and NT Transarc had implemented the NAMEI-interface where you don't need a special fsck. Here everything should be ok. On the other architectures I suggest to use also the NAMEI-interface for some reasons: 1) You get

Re: [OpenAFS] Upgrading Transarc servers

Sorry, I thought I had put more info in the original message. It is Solaris on Sparc and I'm not planning to move to the namei server at this time on that machine. (OK, never on that machine. It needs to be replaced before that happens.) Thanks again, Kevin Depends on the architectures

Re: [OpenAFS] lost contact with volume location server

Have you verified that you don't have any iptables rules that would be blocking AFS packets? Yep. On the worked-at-first-but-not-after-reboot machine, iptables won't even work because there is no support in the kernel. It's firewalled by another machine, but that can't effect it as long as we

Re: [OpenAFS] lost contact with volume location server

If you unload the AFS kernel module before it completely initializes then yes, it will 'oops' the kernel. -derek Peter Schuller [EMAIL PROTECTED] writes: Have you verified that you don't have any iptables rules that would be blocking AFS packets? Yep. On the

Re: [OpenAFS] Errors: Fileserver freezes, Volumes contains orphans

Rubino Geiß schrieb: Hi, Klaas Hagemann reported some problems with dying fileservers. I’ve the sad duty to report another, jet different incident. This morning one of our fileservers (OpenAFS 1.2.8, rh8.0) stopped serving files. Doing bos status, ping, rxdebug and looking at the log files at

Re: [OpenAFS] lost contact with volume location server

If you unload the AFS kernel module before it completely initializes then yes, it will 'oops' the kernel. Ah! Okay. Could that also happen if the afs daemon tried to call the module before it is properly initialized? If so, perhaps that's what is happening - module intialization fails for some

Re: [OpenAFS] lost contact with volume location server

Peter Schuller [EMAIL PROTECTED] writes: If you unload the AFS kernel module before it completely initializes then yes, it will 'oops' the kernel. Ah! Okay. Could that also happen if the afs daemon tried to call the module before it is properly initialized? No. It's not a question of