3 messages in com.perforce.perforce-user[p4] running out of space| From | Sent On | Attachments |
|---|---|---|
| sara...@escalate.com | 24 Apr 2001 09:58 | |
| Stephen Vance | 24 Apr 2001 10:27 | |
| Sebastian Rahtz | 24 Apr 2001 13:20 |
| Subject: | [p4] running out of space![]() |
|---|---|
| From: | Stephen Vance (ste...@vance.com) |
| Date: | 04/24/2001 10:27:25 AM |
| List: | com.perforce.perforce-user |
Chances are that you either did not allocate enough space for your depot, or something in your depot tree is taking lots of space. If either of these is the case, the minor savings you will get from deleting metadata won't save your for long.
I would first look file files that have been submitted binary and see how often new versions are generated. New revisions of binary files are stored in their entirety, not in any differential format. Particularly beware if they are a type like PDF or DOC that is generally compressible, but their perforce type is ubinary. Types like GIF, JPEG and PNG are generally not helped by Perforce compression because they are already pretty well compressed.
You can save space in your metadata, particularly if you have lots of creations and deletions of metadata objects, by checkpointing, backing up, deleting the db.* files and restoring the metadata from the checkpoint. You will need to make sure your users have stopped access while this occurs or new revisions may be lost.
Steve
At 09:58 AM 4/24/2001 -0700, saran.chinnaraj at escalate.com wrote:
Hi all,
We are running out of space on perforce server. I had already started deleting unnecessary labels and client space, is there any other way to increase the space.
Have a good day.
Thanks, Saran
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user
Stephen Vance mailto:steve at vance.com http://www.vance.com/




