We keep Lucene search indexes on a GFS storage volume, mounted cluster-wide. This way each cluster node can perform a search, or append the search index with new content. Works great. Funny thing is, when I list the directory containing the search index, I sometimes see output like the following: $ ls -l total 600 ?--------- ? ? ? ? ? _2931.f3 ?--------- ? ? ? ? ? _2931.f4 -rw-r--r-- 1 toybox toybox 1260 Mar 5 20:21 _2931.f5 ?--------- ? ? ? ? ? _2931.f6 -rw-r--r-- 1 toybox toybox 1261 Mar 5 20:21 _2933.f1 -rw-r--r-- 1 toybox toybox 1261 Mar 5 20:21 _2933.f2 -rw-r--r-- 1 toybox toybox 1261 Mar 5 20:21 _2933.f3 -rw-r--r-- 1 toybox toybox 1261 Mar 5 20:21 _2933.f4 -rw-r--r-- 1 toybox toybox 1261 Mar 5 20:21 _2933.f5 -rw-r--r-- 1 toybox toybox 1261 Mar 5 20:21 _2933.f6 -rw-r--r-- 1 toybox toybox 226300 Mar 5 20:21 _2933.fdt -rw-r--r-- 1 toybox toybox 10088 Mar 5 20:21 _2933.fdx -rw-r--r-- 1 toybox toybox 51 Mar 5 20:21 _2933.fnm -rw-r--r-- 1 toybox toybox 60778 Mar 5 20:21 _2933.frq -rw-r--r-- 1 toybox toybox 43035 Mar 5 20:21 _2933.prx -rw-r--r-- 1 toybox toybox 1571 Mar 5 20:21 _2933.tii -rw-r--r-- 1 toybox toybox 118784 Mar 5 20:21 _2933.tis -rw-r--r-- 1 toybox toybox 0 Mar 5 20:21 commit.lock -rw-r--r-- 1 toybox toybox 0 Mar 5 20:21 deletable -rw-r--r-- 1 toybox toybox 18 Mar 5 20:21 segments -rw-r--r-- 1 toybox toybox 0 Mar 5 20:21 write.lock
I would have expected to see something in each of the fields. Is this a clue that stat() is failing? If so, why? I've never seen anything like it on a non-GFS volume. -Jeff
-- Linux-cluster mailing list Linux-cluster@redhat.com https://www.redhat.com/mailman/listinfo/linux-cluster
