Comment 125 for bug 185311

Hi.

Some of my observations, don't know if helpful:

I found, that i get the locking error on some (not all) files on a NFS-mounted directory.
So i copied that folder to a local disc. Now some files are ok, some other files still
have the error. When i copy and past the file (with nautilus) the error is gone on the copy.
So i deleted the old file and renamed the copy to the old filename. Now the error is there
again. This is reproducable: Copy is ok, error is back again after renaming.

So i went back to the NFS-mounted directory:

Copy / Renaming does not help here.
After playing a bit more, i found, that copying the files to a subdirectory
does help sometimes, sometimes not. In one case the copy to ./tmp had
the error, the copy to ./123 not.

One NFS-file with the locking error was special: It had a german umlaut (ö) in
its name. Copying didn't help, but replacing the ö with o did help. But don't
concentrate on that, i found an other example, where adding an ö 'fixed' the
error.

So now my view into that big crystal ball:
Is there some caching / hashing mechanism in the file locking system,
that depends on filenames and that does its work ..uhm.. sub optimal?

greetings
  Ralf

Is there some