Jump to content

Miles O'Neal

Member Since 28 Oct 2014
Online Last Active Today, 04:59 AM

Topics I've Started

obliterate would only destroy 35 out of 9905 files?

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?

how many sync'd files for a set of clients? (vs locked clients)

11 June 2020 - 09:06 PM

Our db.have is huge. As part of the cleanup effort, I'm looking at how many files various sets of clients have. Most of our clients are locked to an owner, so

   p4 -c <client> have | wc -l

is going to fail.

We do not want to have to unlock (edit) each client to run the have, then relock (edit) the client again. We have lots of user-run and automated scripts that edit clients on the fly, and there's potential for problems if the two processes overlap. While the probability is not high, one of our priorities is that Everything Just Works.

Is there a better way to get this data? I'm somewhat frustrated that superusers don't have a way to universally override a locked client. The -f option is available for *some* commands, but not "p4 have".


list of command:metadata mapping

14 April 2020 - 04:52 PM

I could have sworn that at one point I found a document listing which metadata tables were affected by which commands, but I can't find such a document today. Has anyone seen such a beast, or am I misremembering?


p4 env vars that affect parallel syncs?

06 February 2020 - 09:13 PM

Is there an environment variable that sets the number of parallel threads to use when syncing? I have the server set to default to 4 threads. Some use this but most syncs still use none, while a few use the max of 8. The vast majority of syncs (including most that show up in "p4 monitor show" with 4 or 8 transmit threads) don't log a "--parallel" option.

p4d  2017.1/1534792 on Linux

Best way to prevent use of external symlinks

30 December 2019 - 06:55 PM

We occasionally have someone include a symlink to an external file in their workspace. This might be something in their home dir, a simulation run, etc. Regardless, it then breaks things for others when they sync to the depot containing the symlink[s].

The filesys.checklinks configurable doesn't seem helpful. And I don't see a way to trigger on an add. Have any of you done this?