Re: [OpenAFS] orphaned root.afs problem during 1.3.80 client upgrade

2005-03-30 Thread Hans-Gunther Borrmann
On Wednesday 30 March 2005 19:44, ted creedon wrote: > Yes, root.cell.readonly did disappear on both machines. > Looks like it happened when a vos release on doris_disk.vol id 536870944 > was done from hiawatha . Seems to have created bogus.536870944 id > 536870944 on nanook. The byte count on 536

RE: [OpenAFS] orphaned root.afs problem during 1.3.80 client upgrade

2005-03-30 Thread ted creedon
9.vol hiawatha:/usr/afs/logs # -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hans-Gunther Borrmann Sent: Tuesday, March 29, 2005 11:49 PM To: ted creedon; 'Open AFS' Subject: Re: [OpenAFS] orphaned root.afs problem during 1.3.80 client upgrade On Wed

Re: [OpenAFS] orphaned root.afs problem during 1.3.80 client upgrade

2005-03-29 Thread Hans-Gunther Borrmann
On Wednesday 30 March 2005 04:24, ted creedon wrote: > vos syncvldb is OK on 10.1.1.180 (hiawatha) but a local client doesn't see > the RO cell "bigcell". "Connection timed out" error. I assume that "bigcell" is the mount point for root.cell in your root.afs. If a client wants to access /afs/bigc

[OpenAFS] orphaned root.afs problem during 1.3.80 client upgrade

2005-03-29 Thread ted creedon
During the install of 1.3.80 clients talking to 1.2.11 afs servers, the following was observed:   "Partition vicepa is referenced by VLDB but was not found on server nanook" appears in the windows 1.3.80 AFS server manager GUI.   536870944 is root.afs on nanook (10.1.1.190) and is "orphaned"