On 7 Dec 2009, at 02:48, Albert Hopkins wrote:
...
I tried repeating your experiment, sans NFS and NTFS, and while I did
note that the modification timestamp on the file did not change, the
contents of the file did (i.e. the filesystem changed).
FWIW this is Debian bug #459703 (Google told me that).
What I'm going to guess is happening in your instance is the NFS
server
is caching parts of the file, and it checks the timestamp to see if
the
cache is dirty. Since it doesn't see that file file is modified it
assumes its cache isn't dirty and continues to use it.
You could possibly get away with it by simply
# touch individual.files.img
Maybe, maybe not.
As part of my scheduled maintenance I upgraded my kernel this weekend.
Since I took a little flack a week or two ago for using a .config
plagarised from the Knoppix liveCD, this time I stole one from
systemrescuecd-x86-1.3.1.iso (in fact this is also what I was using
for the NFS client which was able to previously access the loopback
disk image just fine).
Now it's working perfectly, and I'm unable to reproduce the problem.
Many thanks for your help, and I'm sorry I'm unable to document this
issue further,
Stroller.
