NFS weirdness...

[tbs-Gb/NUjX2UK8 at public.gmane.org (ref)]

Hi,

I am using NFS in a production environment to allow multiple front end
servers to access a data server containing Lucene indexes.
Recently, the NFS connections have been acting weird and the index files
got badly corrupted. While investigating, I saw a load of zero byte
files in the NFS mounted directory ...  Is this normal ? what are these
files ? can I bit-bucket them ? are they important ? I have not seen
them before/become aware of them till now ...


-rw-rw-r--  1 production production     0 Apr 15
14:09 .nfs016007720001e150
-rw-rw-r--  1 production production     0 Apr 15
16:10 .nfs016007ea0001e270
-rw-rw-r--  1 production production     0 Apr 16
06:11 .nfs016008e20001e742
-rw-rw-r--  1 production production     0 Apr 16
04:11 .nfs016009a80001e6bc
-rw-rw-r--  1 production production     0 Apr 15
16:10 .nfs01600a270001e246
-rw-rw-r--  1 production production     0 Apr 16
10:09 .nfs01600a560001e85e
-rw-rw-r--  1 production production     0 Apr 15
14:09 .nfs01600a790001e14f
-rw-rw-r--  1 production production     0 Apr 15
14:09 .nfs01600a860001e151
-rw-rw-r--  1 production production     0 Apr 15


any help most welcome (rebuilding lucene indexes is a time consuming
process and I'd rather not have to do it regularly!)

thanks,

Richard
-- 
ref <tbs-Gb/NUjX2UK8 at public.gmane.org>