IOzone on FUSE mount fails when not root

[mtmoore]

The iozone test done during nightly tests fails on Fuse mounts. The issue appears to be related to the file open with mode 0 and the subsequent truncate call. If iozone is modified to specify an 'appropriate' mode the test succeeds. Also, the test succeeds when ran as root. The permission check on the client side indicates it is denying access to truncate the file even though the user running the test is the file owner.

Fuse mount with:
bin/pvfs2fuse -o fs_spec= tcp://<host>:3335/pvfs2-fs,allow_other,umask=022 /tmp/pvfs2-fuse-mount

iozone:
./iozone -a -y 4096 -q $((1024*16)) -n 4096 -g $((1024*16*2)) -f /tmp/pvfs2-fuse-mount/iozone.out

Current work around is to run the test as root for FUSE mounts