Jump to content


obliterate would only destroy 35 out of 9905 files?

obliterate

  • Please log in to reply
1 reply to this topic

#1 Miles O'Neal

Miles O'Neal

    Advanced Member

  • Members
  • PipPipPip
  • 214 posts
  • LocationAustin. Texas. Y'all.

Posted 18 June 2020 - 10:42 PM

I'm trying to test obliterate times on an older p4d vs a new one. I've cloned the production data and was ready, I thought, for the timed tests. But "p4 obliterate" (no "-y" yet) thinks it only needs to destroy 35 files (including versions), whereas "p4 files" tells me there are 9905 files there. Only 31 of the files are not "branch change" files; these seem to be the ones being obliterated. Obliterate with "-b" lists no files.

"p4 snap -n" found no files that need to be snapped.

As expected, it makes no difference in the output whether I use a client or not. (Client is faster, of course,)


% p4 obliterate //moneal_reusable_oblit/...
[35 files listed]
Would delete 1818296 client 19760 integration 9935 revision record(s).
This was report mode.  Use -y to remove files.
% p4 obliterate -b //moneal_reusable_oblit/...
Would delete 1816816 client 19748 integration 9874 revision record(s).
This was report mode.  Use -y to remove files.


What's going on here? Is it really going to delete all the files but just not list them?

#2 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 1192 posts

Posted 19 June 2020 - 12:42 AM

Obliterate only outputs the individual revisions that will be "purged" from the depot archive (i.e. unique revisions that you're obliterating the only/last reference to).  All of the files will be removed from the metadata, as indicated by the summary output.





Also tagged with one or more of these keywords: obliterate

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users