[OpenAFS] Help wanted (vos release/volume locked)

[Lars Schimmer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Horst Birthelmer schrieb:
|
| On Nov 5, 2004, at 3:10 PM, Lars Schimmer wrote:
|
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|> Hi!
|>
|> I've got some problems:
|> vos examine office
|> office                            536871143 RW     662181 K  On-line
|> ~    zork.cg.cs.tu-bs.de /vicepb
|> ~    RWrite  536871143 ROnly  536871144 Backup          0
|> ~    MaxQuota    1024000 K
|> ~    Creation    Tue May 18 15:28:06 2004
|> ~    Last Update Fri Nov  5 14:41:38 2004
|> ~    582 accesses in the past day (i.e., vnode references)
|>
|> ~    RWrite: 536871143     ROnly: 536871144     RClone: 536871144
|> ~    number of sites -> 3
|> ~       server zork.cg.cs.tu-bs.de partition /vicepb RW Site  -- New
|> release
|> ~       server triton.cg.cs.tu-bs.de partition /vicepa RO Site  -- New
|> release
|> ~       server tetris.cg.cs.tu-bs.de partition /vicepb RO Site  -- Old
|> release
|> ~    Volume is currently LOCKED
|>
|> So I wanted to release this volume:
|> vos release office
|> Could not lock the VLDB entry for the volume 536871143.
|> VLDB: vldb entry is already locked
|> Error in vos release command.
|> VLDB: vldb entry is already locked
|>
|> Even a vos remsite doesn't work.
|> Anyone has a tip how to remove this lock and release this office-volume?
|> I even tried to release the root.cell and root.afs volumes, with no
|> effect.
|> I use 1.3.73 on Debian or 1.2.11 on RedHat.
|>
|
| After figuring out why it became that way in the first place ...
|
| vos unlock -id office

Uuups. Slap myself with the 9-cat5-whip.
RTFM is always the best ;-)
Why it was locked, a big mystery.
At least a try a bit around with the 1.3.73 .deb in experimental (yeah, I know
why it is called experimental), here local on 2.4.27. That special version seems
to get the local servername from the 127.0.0.1 entry in /etc/hosts, which was
VERY bad, because it was set to localhost. So the backup was set on localhost in
the vldb. And that run for two days this way. Maybe thats why it's locked, maybe
not...
But after changing the /etc/hosts, the vldb was right with my servername, but
the lock was still there.
By side I test this .deb on 2.6.9 Kernel, client seems to work with no flaw (no
error till yet), but the server...It seems to work, but with a vos examine I had
some funny servername in the vldb (which weren't in the hosts file, funny).

| Horst

Thx for your help to my stupid question ;-)

Cya
Lars
- --
- -----------------------------------------------------------------
Technische Universität Braunschweig, Institut für Computergraphik
Tel.: +49 531 391-2109            E-Mail: schimmer@cg.cs.tu-bs.de
PGP-Key-ID: 0xB87A0E03


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBi47JVguzrLh6DgMRAiimAKC2umthj3pNH6ZYuDNkfHamfkVrxQCdF0uk
+S7MrzHENd1qYcQTww1oKG4=
=mjcR
-----END PGP SIGNATURE-----