Thousands of modified files

Folks,

We are seeing thousands of modified files in different workarea's in the branch. We have multiple workarea's under a single branch and all of sudden when the user navigates to his workarea and perform "modified files" it shows 200k+ files modified. Lets say the file has a version number of 23, after this mess the version numbers shows as 0+ but still shows the rest of the 23 version in the version history.

Has anybody encountered anything like this before.

Thanks for your help.

Pradeep

Find more posts tagged with

Comments

bagman

Has this been a recurring issue? I am seeing a similar issue.

I submit a file and it is no longer modified. At some point later, the file shows back up as modified, yet the timestamp, size and content has not changed. I am not seeing the version issue you described. My versions are correct (e.g. 23+ instead of 0+ [new file]). The system shows the file last modified by root.

I wrote a cron job to monitor a particular file and determined when the file changed. Yet, I have not been able to nail down a process that was running at that time. There is nothing in the TeamSite logs showing activity at that time.

Does anyone know what could trigger a file to be flagged as modified by TeamSite, but not by the filesystem (i.e. timestamp not updated)?

Adam Stoller

Has this been a recurring issue? I am seeing a similar issue.

I submit a file and it is no longer modified. At some point later, the file shows back up as modified, yet the timestamp, size and content has not changed. I am not seeing the version issue you described. My versions are correct (e.g. 23+ instead of 0+ [new file]). The system shows the file last modified by root.

I wrote a cron job to monitor a particular file and determined when the file changed. Yet, I have not been able to nail down a process that was running at that time. There is nothing in the TeamSite logs showing activity at that time.

Does anyone know what could trigger a file to be flagged as modified by TeamSite, but not by the filesystem (i.e. timestamp not updated)?

Things that might cause this:

bagman

[QUOTE=ghoti]Things that might cause this:

Thanks ghoti. I have been suspicious of the backup process myself. I don't believe they are properly freezing the backing store prior to running the backup.I had not thought about anti-virus though. I will need to follow up to see if they are running that type of process.Thanks,Mark