[p4] NFS mounted depot
david.weintraub at bofasecurities.com
Tue Feb 21 08:53:14 PST 2006
My understanding is that it is more than whether or not the p4d daemon
has access to the disks. It has to do with the file locking nature of
NFS disks. Since all reads and writes come only from a single server, I
didn't think this would be much of an issue for the RCS files, and
thought it might only affect the *.db files. That's why I called
Neither IT nor I are overly concerned with the *.db files and the
journal being placed on local disks. They can support that easily
enough. As long as we checkpoint on a daily basis and store this
checkpoint file on the NFS disks, we really don't need the local disks
backed up. However, we may have a problem if the entire Perforce depot
has to be on local disks since we would have to back that up.
I really need Perforce to clarify this issue.
From: Paul Goffin [mailto:Paul.Goffin at aepnetworks.com]
Sent: Tuesday, February 21, 2006 10:36 AM
To: Weintraub, David; Smith, Jeff; perforce-user at perforce.com
Subject: RE: [p4] NFS mounted depot
>As a person who once worked in an IT department, I remember being on
> other side of the battle line. Why can't you people just get us more
> disk space? Why is diskspace so expensive? I can by a 100 gigabyte
> from CompUSA for $110 and you guys want to charge me 10 times that
> rate? I need to run my application on an X type of drive. Why can't
> guys get your act together and give that to me? Where am I suppose to
> store my MP3s I downloaded?
No one is saying you need to spend $10, $100 or $1000 on disks. What
needs to be done is the p4d demon is run on a server that has direct
access to one of those NFS disks you're trying to use.
More information about the perforce-user