[OpenAFS] Possible vos bug still in 1.6.0pre3?

Ryan C. Underwood nemesis@icequake.net
Wed, 16 Mar 2011 00:59:06 -0500


On Wed, Mar 16, 2011 at 01:49:35AM -0400, Derrick Brashear wrote:
> > =A0 Server ip addr 5 =3D 0.0.0.2
>=20
> which is the problem.... but is a legit ip.

Ah, I get it then.  vos isn't doing the wrong thing, it's just acting on
bad data.

> > adm_clientbackup
> > =A0 =A0RWrite: 536871269
> > =A0 =A0number of sites -> 1
> > =A0 =A0 =A0 server 0.0.0.2 partition /vicepb RW Site
>=20
> and that's really what's in the database.

How do I fix it?  I know where the volume is, it just seems like the
VLDB entry is messed up.  The volume header seems to indicate that the
rename never actually took place except in the VLDB.

# volinfo /vicepb 0536871269
Inode 2305844542651236351: Good magic 78a1b2c5 and version 1
Inode 2305844542718345215: Good magic 99776655 and version 1
Inode 2305844542785454079: Good magic 88664433 and version 1
Inode 2305844542986780671: Good magic 99877712 and version 1
Volume header for volume 536871269 (adm_backup)
stamp.magic =3D 78a1b2c5, stamp.version =3D 1
inUse =3D 0, inService =3D 1, blessed =3D 1, needsSalvaged =3D 0, dontSal=
vage =3D 0
type =3D 0 (read/write), uniquifier =3D 2958, needsCallback =3D 0, destro=
yMe =3D 0
id =3D 536871269, parentId =3D 536871269, cloneId =3D 0, backupId =3D 0, =
restoredFromId =3D 0
maxquota =3D 0, minquota =3D 0, maxfiles =3D 0, filecount =3D 1279, disku=
sed =3D 33224265
creationDate =3D 1246401783 (2009/06/30.17:43:03), copyDate =3D 129954915=
0 (2011/03/07.19:52:30)
backupDate =3D 0 (1969/12/31.18:00:00), expirationDate =3D 0 (1969/12/31.=
18:00:00)
accessDate =3D 1299704176 (2011/03/09.14:56:16), updateDate =3D 129957115=
0 (2011/03/08.01:59:10)
owner =3D 0, accountNumber =3D 0
dayUse =3D 7; week =3D (3102, 5883, 0, 0, 0, 0, 0), dayUseDate =3D 129965=
0400 (2011/03/09.00:00:00)
volUpdateCounter =3D 1386

--=20
Ryan C. Underwood, <nemesis@icequake.net>