[OpenAFS] vldb_check -servers cleanup and empty server entry
messages
John W. Sopko Jr.
sopko@cs.unc.edu
Tue, 02 Mar 2010 08:20:09 -0500
I did a "bos restart server vldb" on our 3 db server machines,
did not help.
I did a "vos syncvldb" and "vos syncserv" on our file servers and
this did not help.
I copied the /usr/afs/db/vldb.DB0 file and
tried "vldb_check vldb.DB0 -fix " and this did not help.
Do I need to worry about all the "index 0-12 points to empty
server entry 0" I am getting?
Can someone try to run ""vldb_check -servers" against there
/usr/afs/db/vldb.DB0 or a copy of the database file and see if they get any of
the
empty server entry messages or bogus server ip addr entries.
Thanks.
John W. Sopko Jr. wrote, On 2/25/2010 4:08 PM:
> I am planning a move of our primary db server (lowest IP). I wanted to
> check
> the db's. I ran the vldb_check /usr/afs/db/vldb.DB0 and things seemed to
> be fine:
>
> % vldb_check /usr/afs/db/vldb.DB0
> VLDB_CHECK_WARNING: Ubik header size is 0 (should be 64)
> Scanning 3385 entries for possible repairs
>
> Being curious I ran vldb_check with the -servers option to see what
> file servers were registered and saw this:
>
> % vldb_check /usr/afs/db/vldb.DB0 -servers |& head -40
> VLDB_CHECK_WARNING: Ubik header size is 0 (should be 64)
> MH block 0, index 1: 152.2.128.4
> MH block 0, index 3: 152.2.128.3
> MH block 0, index 4: 152.2.129.145
> MH block 0, index 31: 152.2.129.25
> MH block 0, index 32: 152.2.128.34
> Server ip addr 4 = 152.2.128.157
> Server ip addr 5 = 152.2.128.161
> Server ip addr 6 = 152.2.128.57
> Server ip addr 7 = 152.2.128.159
> Server ip addr 9 = 152.2.128.128
> Server ip addr 10 = 152.2.128.11
> Server ip addr 11 = 152.2.128.20
> Server ip addr 12 = 152.2.128.155
> Server ip addr 13 = MH block 0, index 4
> Server ip addr 14 = 152.2.128.91
> Server ip addr 15 = 152.2.128.28
> Server ip addr 16 = 152.2.128.24
> Server ip addr 19 = 152.2.128.248
> Server ip addr 21 = MH block 0, index 3
> Server ip addr 22 = MH block 0, index 1
> Server ip addr 24 = 152.2.128.249
> Server ip addr 47 = MH block 0, index 31
> Server ip addr 48 = MH block 0, index 32
>
> The entries like "Server ip addr ..." our not file or db servers and in
> some cases are not in DNS. These IPs are owned by us but our not
> file servers.
>
> The entries like "MH block 0, index ..." are indeed our db and file
> servers accept for one of the entries which is our kerberos 5 server and
> it is
> not a file server.
>
> The "vos listaddresss" shows the fire 5 "MH block 0" servers.
>
> Previous to this vldb_check I ran another check and there were 4
> "server ip addr ..." entries that were not in the IP range we own or DNS.
> I used "vos changeadress 128.109.136.161 -remove" to remove the 4 entries.
>
> I then ran vldb_check /usr/afs/db/vldb.DB0 -servers again, the
> entries were removed but I now get a bunch of "empty server entry 0"
> entries!
> A sample of a few entries is shown below. The volumes that are
> displayed seem to be fine. It is making me nervous!
>
> I did a "vos syncvldb", vos syncserver" and a "bos salvage" on one of
> the volumes but is still shows up with 13 "empty server entry 0" lines
> in the vldb_check output.
>
> Is there a way to clean this up?
>
> Should I remove the other "Server ip addr .." entries that are
> not db or file servers? Thanks for any help.
>
>
> % vldb_check /usr/afs/db/vldb.DB0 -servers | & head -80
> VLDB_CHECK_WARNING: Ubik header size is 0 (should be 64)
> MH block 0, index 1: 152.2.128.4
> MH block 0, index 3: 152.2.128.3
> MH block 0, index 4: 152.2.129.145
> MH block 0, index 31: 152.2.129.25
> MH block 0, index 32: 152.2.128.34
> Server ip addr 4 = 152.2.128.157
> Server ip addr 5 = 152.2.128.161
> Server ip addr 6 = 152.2.128.57
> Server ip addr 7 = 152.2.128.159
> Server ip addr 9 = 152.2.128.128
> Server ip addr 10 = 152.2.128.11
> Server ip addr 11 = 152.2.128.20
> Server ip addr 12 = 152.2.128.155
> Server ip addr 13 = MH block 0, index 4
> Server ip addr 14 = 152.2.128.91
> Server ip addr 15 = 152.2.128.28
> Server ip addr 16 = 152.2.128.24
> Server ip addr 19 = 152.2.128.248
> Server ip addr 21 = MH block 0, index 3
> Server ip addr 22 = MH block 0, index 1
> Server ip addr 24 = 152.2.128.249
> Server ip addr 47 = MH block 0, index 31
> Server ip addr 48 = MH block 0, index 32
> Volume 'root.afs', index 0 points to empty server entry 0
> Volume 'root.afs', index 1 points to empty server entry 0
> Volume 'root.afs', index 2 points to empty server entry 0
> Volume 'root.afs', index 3 points to empty server entry 0
> Volume 'root.afs', index 4 points to empty server entry 0
> Volume 'root.afs', index 5 points to empty server entry 0
> Volume 'root.afs', index 6 points to empty server entry 0
> Volume 'root.afs', index 7 points to empty server entry 0
> Volume 'root.afs', index 8 points to empty server entry 0
> Volume 'root.afs', index 9 points to empty server entry 0
> Volume 'root.afs', index 10 points to empty server entry 0
> Volume 'root.afs', index 11 points to empty server entry 0
> Volume 'root.afs', index 12 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 0 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 1 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 2 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 3 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 4 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 5 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 6 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 7 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 8 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 9 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 10 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 11 points to empty server entry 0
> Volume 'W0.prj.mip.vars', index 12 points to empty server entry 0
> Volume 'D4.home.ianzola', index 0 points to empty server entry 0
> Volume 'D4.home.ianzola', index 1 points to empty server entry 0
> Volume 'D4.home.ianzola', index 2 points to empty server entry 0
> Volume 'D4.home.ianzola', index 3 points to empty server entry 0
> Volume 'D4.home.ianzola', index 4 points to empty server entry 0
> Volume 'D4.home.ianzola', index 5 points to empty server entry 0
> Volume 'D4.home.ianzola', index 6 points to empty server entry 0
> Volume 'D4.home.ianzola', index 7 points to empty server entry 0
> Volume 'D4.home.ianzola', index 8 points to empty server entry 0
> Volume 'D4.home.ianzola', index 9 points to empty server entry 0
> Volume 'D4.home.ianzola', index 10 points to empty server entry 0
> Volume 'D4.home.ianzola', index 11 points to empty server entry 0
> Volume 'D4.home.ianzola', index 12 points to empty server entry 0
> Volume 'D4.home.sgillon', index 0 points to empty server entry 0
> Volume 'D4.home.sgillon', index 1 points to empty server entry 0
> Volume 'D4.home.sgillon', index 2 points to empty server entry 0
> Volume 'D4.home.sgillon', index 3 points to empty server entry 0
> Volume 'D4.home.sgillon', index 4 points to empty server entry 0
> Volume 'D4.home.sgillon', index 5 points to empty server entry 0
> Volume 'D4.home.sgillon', index 6 points to empty server entry 0
> Volume 'D4.home.sgillon', index 7 points to empty server entry 0
> Volume 'D4.home.sgillon', index 8 points to empty server entry 0
> Volume 'D4.home.sgillon', index 9 points to empty server entry 0
> Volume 'D4.home.sgillon', index 10 points to empty server entry 0
> Volume 'D4.home.sgillon', index 11 points to empty server entry 0
> Volume 'D4.home.sgillon', index 12 points to empty server entry 0
>
> and many more ....
>
>
>
--
John W. Sopko Jr. University of North Carolina
email: sopko AT cs.unc.edu Computer Science Dept., CB 3175
Phone: 919-962-1844 Fred Brooks Building; Room 140
Fax: 919-962-1799 Chapel Hill, NC 27599-3175