[p4] Deleteting/getting new Files (CALL#1468508)

[Hamid Ghassemi]

The client workspace is locally and not attached to NFS nor SAN

-----Original Message-----
From: Smith, Jeff [mailto:jsmith at medplus.com] 
Sent: Tuesday, October 24, 2006 1:48 PM
To: Hamid Ghassemi; Joshua Eror; Robert McKenna; Perforce Users
Subject: RE: [p4] Deleteting/getting new Files (CALL#1468508)

I guess one possibility is some weird file system error.  Is the client
workspace locally attached disk, NFS, SAN...?

Jeff

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Hamid Ghassemi
Sent: Tuesday, October 24, 2006 12:01 PM
To: Joshua Eror; Robert McKenna; Perforce Users
Subject: Re: [p4] Deleteting/getting new Files (CALL#1468508)


Thanks for the response.  

However, the client Spec is not being used on multiple hosts; rather it
is used on only one host.  The problem is when a user is using the same
client spec with p4 command line, eclipse plugin or P4v on the same
host.  This problem does not happen for everyone.  Also I have seen this
problem with a user using only p4v and a single client spec.  I have had
to remove his client and have him create a new client.  Incidentally, he
was a new user who created one client spec and this problem showed up at
his first try.  I have checked our server and cannot see any problems
with it.

Hamid

-----Original Message-----
From: Joshua Eror [mailto:support at perforce.com] 
Sent: Monday, October 23, 2006 10:56 PM
To: Robert McKenna; Hamid Ghassemi; Perforce Users
Subject: Re: [p4] Deleteting/getting new Files (CALL#1468508)

Hi Hamid,


On Mon, 23 Oct 2006 16:40:43 -0600 "Robert McKenna"
<robertm at bioware.com> said:
> -- Message moved from call # 1469070 by laurette --
> 
> You will get both of those problems if a client spec is being used on 
> more than one host, that is if the host is not set in the client 
> specfication. You will also get the latter problem is users do not use

> Perforce to remove files from their machine.
> 
> Rob McKenna


Ron makes a very astute observation here. Sharing a single workspace
across multiple machines, or overlapping multiple workspace roots, is
sure to result in odd behaviour. It's import to verify that user work
flow is not straying outside recommended practices.


>  -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Hamid
Ghassemi
> Sent: Monday, October 23, 2006 12:20 PM
> To: Perforce Users
> Cc: support at perforce.com
> Subject: [p4] Deleteting/getting new Files
> 
> We seem to have a problem deleting files in some of our workspaces. 
> When a user deletes a file from the depot using p4 delete or via p4v
or
> via a plugin in eclipse, other users cannot remove the file from their

> workstations after performing a sync via any of the above options. 
> Although Perforce reports all files are up to date and it indicates
that
> the files are removed from the local workspace.
> 
> We have been able to get around this problem with either removing the 
> client workspace and recreating it, or syncing to the revision prior
to
> the one before the sync and then sync to the HEAD and then the file is

> removed.
> 
> We have also seen files not being synced to the latest even though the

> server reports that they are.
> 
> Has anyone seen these problems with P4?  We are using the latest
version
> of P4V.
> 
> Thanks
> 
> Hamid Ghassemi


Regards,

--
Get the most of your SCM system -- take the Perforce Product Training.
See http://www.perforce.com/perforce/training.html for more information.
---
Josh Eror
Perforce Software Technical Support
support at perforce.com
(510) 864-7400

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user