[p4] Delete depot problem
Sweeney, Tony
sweeney at ea.com
Fri Dec 1 07:51:34 PST 2006
Paul,
I'd be suspicious of database corruption at this point. What
does 'p4 files //MyDepot/...' tell you? 'p4 verify //MyDepot/...'? On
the server, 'p4d -xx'? (Set your environment or pass appropriate
command line parameters -- this does an internal database consistency
check.)
Tony.
quis custodiet ipsos custodes -- Juvenal VI, 347-8
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Paul
> M. Goorskis
> Sent: 01 December 2006 14:55
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Delete depot problem
>
>
> Hi David,
>
> How could I check for this? I've removed all clients who worked with
> this depot, but i could miss something.
>
> David Weintraub wrote:
>
> > Anything opened on that depot? Any pending changelists that have
> > something on that depot?
> >
> > On 12/1/06, Paul M. Goorskis <pmg at rimako.lv> wrote:
> >
> >> $ 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