Yes. The data area is on our lustre-based storage, which for all
practical purposes in ordinary data access behaves as Posix I/O. This
does not seem to be the case for whatever ldmadmin is trying to do,
however. If I move teh data area to a purely local disk, I do not get
the F_WRLCK error from pqcreate, but still get a "mkqueue failed" error:
-bash-3.00$ ls -ltr
total 688
-rw-r--r-- 1 ldm tigre 637868 May 23 15:42 ldm-6.6.4.tar.gz
drwxr-xr-x 7 ldm tigre 4096 May 23 15:52 ldm-6.6.4
lrwxrwxrwx 1 ldm tigre 9 May 23 15:58 runtime -> ldm-6.6.4
lrwxrwxrwx 1 ldm tigre 11 May 23 16:00 src -> runtime/src
lrwxrwxrwx 1 ldm tigre 11 May 23 16:00 man -> runtime/man
lrwxrwxrwx 1 ldm tigre 11 May 23 16:00 lib -> runtime/lib
lrwxrwxrwx 1 ldm tigre 15 May 23 16:00 include -> runtime/include
lrwxrwxrwx 1 ldm tigre 11 May 23 16:00 bin -> runtime/bin
drwxr-xr-x 2 ldm tigre 4096 May 23 17:40 etc
drwxr-xr-x 2 ldm tigre 4096 May 23 17:55 logs
drwxr-xr-x 2 ldm tigre 4096 May 23 17:58 data
-bash-3.00$ ldmadmin mkqueue -v
Creating /usr/local/ldm/data/ldm.pq, 400000000 bytes, 97656 products.
May 23 23:03:42 UTC wiglaf.hpcc.ttu.edu : make_pq: mkqueue failed
The file was apparently created, so why the "mkqueue failed" message?
-bash-3.00$ ls -l data
total 402120
-rw-r--r-- 1 ldm tigre 411357184 May 23 18:03 ldm.pq