On Thu, 6 May 2010 13:42:14 +0300 (EEST)
Atro Tossavainen wrote:
> Giving the file servers another IP and moving things to that may be
> more intrusive than shutting down vlservers for a while (depending on
> the definition of "a while", of course) if the clients have anything
> like a hard time
On Thu, 06 May 2010 10:43:47 +0200 (CEST)
Harald Barth wrote:
> > The vlserver could really use a safety check to prevent adding
> > duplicate addresses so this doesn't happen; I'll look into that.
>
> My guess is that you only can get into that state if you have a vldb
> that has a mix of old s
Andrew,
> Oops, yeah, sorry. You don't see the error messages I'm thinking of
> unless you're at debug level 5 or higher (run vlserver with '-d 5', or
> send it two 'kill -TSTP's). But I think I know what it will say. It will
> also suggest you to either 'vos changeaddr' the old address, or to
> d
Andrew,
> So, you need to remove one of those duplicates. The problem is, the only
> way of specifying a server to remove from the VLDB is by IP address, so
> we can't specify a specific one of those duplicates, since they have the
> same IP. I don't think this will work, but you can try
>
> vos
> The vlserver could really use a safety check to prevent adding
> duplicate addresses so this doesn't happen; I'll look into that.
My guess is that you only can get into that state if you have a vldb
that has a mix of old style entries without UUIDs and new ones. If you
have had a VLDB for a lon
On Tue, 4 May 2010 11:09:11 -0500
Andrew Deason wrote:
> > r...@bond / 17 # vldb_check -database /usr/afs/db/vldb.DB0 -servers
> > VLDB_CHECK_WARNING: Ubik header size is 0 (should be 64)
> > MH block 0, index 1: 128.214.58.174
> > MH block 0, index 2: 128.214.88.114
> >Server ip addr 0 = MH
On Tue, 4 May 2010 08:45:23 +0300 (EEST)
Atro Tossavainen wrote:
> > My guess is that this would be the result of using 'vos changeaddr',
> > or at least something with MH vs non-MH hosts.
>
> MH, non-MH?
MH for 'multihomed'. "Old" VLDB server entries just map a server number
to a server IP. A
Thanks all,
* Yes, I know kaserver is deprecated, thank you
* To repeat, running IBM AFS anything on Solaris 10 x64 is not possible
* Running kaserver on hosts other than the current two means running
all the database services of AFS on hosts other than the current
two, which leads to all th
On Mon, 3 May 2010 15:23:29 +0300 (EEST)
Atro Tossavainen wrote:
> Mon May 3 15:18:31 2010 VL_RegisterAddrs rpc failed; The IP address exists
> on a different server; repair it
> Mon May 3 15:18:31 2010 VL_RegisterAddrs rpc failed; See VLLog for details
My guess is that this would be the resu
