[p4] db.label and p4d verify -xv.

[Brad Holt]

You won't see the metadata shrink until you restore from a checkpoint.

I would restore from a checkpoint first and then try the obliterate (I
always do this for larger obliterate operations).  If you first restore
from your checkpoint, then the obliterate may run faster as it will have
less to wade through in the .have and .label.  Also, perhaps it will
give you a clue as to what the problem with your corrupted message.
It's been my experience that if checkpoints are being successfully
taken, then your metadata is probably OK.  I know there can be
exceptions.  Anyway, all this is assuming that you have been
successfully checkpointing the database.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Raghu Kumar C
Sent: Wednesday, January 31, 2007 4:49 AM
To: perforce-user at perforce.com
Subject: [p4] db.label and p4d verify -xv.
Importance: High

Hi All,

	I have three doubts. It would be nice if someone could answer
this.

- I had around 2000 labels in my depot and the db.label file size was
around 18GB. Now I have deleted around 800 labels from it; but the
db.label file still shows me the same size. Why is it that the size of
db.label file remains the same?

- If I run p4d verify -xv command will it lock the perforce DB?

- Is it safe to run p4d verify -xv -xr (repair)? I think my db.have file
is corrupted. I get the db.have file corrupt error when I try to
obliterate a file.

	Thanking you in advance for your time and effort.

Thank you,
Raghu

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user