[p4] Delete depot problem

Russell C. Jackson rusty at rcjacksonconsulting.com
Fri Dec 1 16:32:50 PST 2006


You can try running p4d -xf 925 to see if that turns up any lock 
problems. It will fix them if it does.

Thanks,
Rusty

--------------------------------------------------
RCJackson Consulting
Perforce Consulting Partner and Certified Trainer
--------------------------------------------------
rusty at rcjacksonconsulting.com
http://www.rcjacksonconsulting.com
tel:      479-696-9710
fax:      479-967-0963
mobile:   479-747-3845
--------------------------------------------------




Stanton Stevens wrote:
> I've run into this several times. It is probably old lock records that
> didn't get deleted along with the files. Ask Perforce tech support how
> to get the lock records for that depot out of the checkpoint, convert
> them into "dv" lines, and restore them as you would a journal file. Then
> you will be probably be able to delete the depot. 
>
> Stanton 
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Paul M.
> Goorskis
> Sent: Friday, December 01, 2006 12:35 AM
> To: perforce-user at perforce.com
> Subject: [p4] Delete depot problem
>
> $ p4 depot -d MyDepot
> Depot MyDepot isn't empty; clear it with 'p4 obliterate' first.
> $ p4 obliterate -y //MyDepot/...
> No records to delete.
>
>
> Server version: P4D/LINUX26X86/2006.1
> Kernel version: Linux perforce 2.6.9-5.ELsmp
> FS Type: ext3
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
>
>   


More information about the perforce-user mailing list