Odd behaviour for random files

Issue #15 invalid
Jan Olsen
created an issue

Lately I started to experience some very odd behaviour with one of my repositories.

I have three separate repositories on three different mapped network drives (all running windows). Two of the repositories works flawlessly, but the third is... well... acting strange :(.

Out of nowhere some random file are suddenly marked as modified:
{{{
X:>hg status .
M axysmail.lst
}}}

Running a diff on the same file:
{{{
X:>hg diff axysmail.lst
diff -r bde740cb546b axysmail.lst
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/axysmail.lst Wed Apr 06 10:37:42 2011 +0200
@@ -0,0 +1,1 @@
(this line is intentionally deleted for privacy purposes)
}}}
The file is clearly marked as "modified", but somehow mercurial fails to find the file in the repository.

Viewing a log of that specific file shows that it indeed should be in the repository:
{{{
X:>hg log axysmail.lst
changeset: 202:e458e0724a5d
user: xxx
date: Fri Feb 05 13:34:32 2010 +0100
summary: infra alignment

changeset: 123:baf9cabed797
user: xxx
date: Wed Jan 20 14:47:26 2010 +0100
summary: infra alignment
}}}

While the repository contains a large number of files then there aren't that many changesets:
{{{
X:>hg tip
changeset: 1237:bde740cb546b
tag: tip
user: xxx
date: Wed Apr 06 09:55:37 2011 +0200
summary: Debug txt and fix for non-value
}}}

Also there shouldn't be anything wrong with the repository according to the verify command:
{{{
X:>hg -v verify --time
repository uses revlog format 1
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
37901 files, 1238 changesets, 47734 total revisions
Time: real 392.241 secs (user 42.969+0.000 sys 26.328+0.000)
}}}

I do have a virus checker running which might touch/scan the above mentioned file and the file itself is also a part of a batch script and are created automatically every single day. However the contents of the file hasn't changed the last couple of months - so only the timestamp is changed.

All the above commands has been run with the latest version of mercurial:
{{{
X:>hg --version
Mercurial Distributed SCM (version 1.8.2)
}}}

Do you have any idea of what is happening or why it has suddenly started behaving like this?

Comments (3)

  1. Log in to comment