for v3 mount a lot more test cases got failed

/export/opt/qa/tools/pjd-fstest-20080816/tests/chmod/00.t   (Wstat: 0 Tests: 58 Failed: 3)
  Failed tests:  12, 33, 45
/export/opt/qa/tools/pjd-fstest-20080816/tests/chown/00.t   (Wstat: 0 Tests: 170 Failed: 7)
  Failed tests:  8, 83, 87, 103, 125, 146, 162
/export/opt/qa/tools/pjd-fstest-20080816/tests/link/00.t    (Wstat: 0 Tests: 80 Failed: 3)
  Failed tests:  28, 61, 74
/export/opt/qa/tools/pjd-fstest-20080816/tests/link/10.t    (Wstat: 0 Tests: 14 Failed: 1)
  Failed test:  11
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkdir/00.t   (Wstat: 0 Tests: 36 Failed: 2)
  Failed tests:  33-34
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkdir/10.t   (Wstat: 0 Tests: 12 Failed: 1)
  Failed test:  10
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkfifo/00.t  (Wstat: 0 Tests: 36 Failed: 11)
  Failed tests:  2, 5, 8, 11, 14, 18, 21, 25, 29, 33-34
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkfifo/02.t  (Wstat: 0 Tests: 3 Failed: 1)
  Failed test:  1
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkfifo/03.t  (Wstat: 0 Tests: 11 Failed: 1)
  Failed test:  5
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkfifo/05.t  (Wstat: 0 Tests: 12 Failed: 2)
  Failed tests:  4, 9
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkfifo/06.t  (Wstat: 0 Tests: 12 Failed: 2)
  Failed tests:  4, 9
/export/opt/qa/tools/pjd-fstest-20080816/tests/mkfifo/09.t  (Wstat: 0 Tests: 12 Failed: 1)
  Failed test:  10
/export/opt/qa/tools/pjd-fstest-20080816/tests/open/00.t    (Wstat: 0 Tests: 47 Failed: 2)
  Failed tests:  33-34
/export/opt/qa/tools/pjd-fstest-20080816/tests/open/17.t    (Wstat: 0 Tests: 3 Failed: 1)
  Failed test:  1
/export/opt/qa/tools/pjd-fstest-20080816/tests/open/22.t    (Wstat: 0 Tests: 12 Failed: 1)
  Failed test:  7
/export/opt/qa/tools/pjd-fstest-20080816/tests/rename/00.t  (Wstat: 0 Tests: 79 Failed: 7)
  Failed tests:  22, 49, 53, 55, 57, 61, 71
/export/opt/qa/tools/pjd-fstest-20080816/tests/rename/09.t  (Wstat: 0 Tests: 56 Failed: 4)
  Failed tests:  23, 27, 31, 35
/export/opt/qa/tools/pjd-fstest-20080816/tests/rename/10.t  (Wstat: 0 Tests: 188 Failed: 14)
  Failed tests:  12, 27, 42, 83-84, 98-99, 113-114, 128-129
                144, 159, 174
/export/opt/qa/tools/pjd-fstest-20080816/tests/rename/13.t  (Wstat: 0 Tests: 17 Failed: 1)
  Failed test:  7
/export/opt/qa/tools/pjd-fstest-20080816/tests/rename/14.t  (Wstat: 0 Tests: 17 Failed: 1)
  Failed test:  7
/export/opt/qa/tools/pjd-fstest-20080816/tests/rename/20.t  (Wstat: 0 Tests: 16 Failed: 1)
  Failed test:  9
/export/opt/qa/tools/pjd-fstest-20080816/tests/rmdir/00.t   (Wstat: 0 Tests: 10 Failed: 2)
  Failed tests:  8-9
/export/opt/qa/tools/pjd-fstest-20080816/tests/rmdir/01.t   (Wstat: 0 Tests: 14 Failed: 1)
  Failed test:  12
/export/opt/qa/tools/pjd-fstest-20080816/tests/rmdir/06.t   (Wstat: 0 Tests: 20 Failed: 1)
  Failed test:  17
/export/opt/qa/tools/pjd-fstest-20080816/tests/symlink/00.t (Wstat: 0 Tests: 14 Failed: 2)
  Failed tests:  11-12
/export/opt/qa/tools/pjd-fstest-20080816/tests/unlink/00.t  (Wstat: 0 Tests: 55 Failed: 10)
  Failed tests:  10, 19, 28, 35-36, 39, 41-42, 47-48
/export/opt/qa/tools/pjd-fstest-20080816/tests/unlink/11.t  (Wstat: 0 Tests: 33 Failed: 4)

On the latest release dev-26,for vfs on v4 mount only following tests were failing

/home/jiffin/qa/tools/pjd-fstest-20080816/tests/chown/00.t   (Wstat: 0 Tests: 170 Failed: 2)
  Failed tests:  83, 87
/home/jiffin/qa/tools/pjd-fstest-20080816/tests/open/07.t    (Wstat: 0 Tests: 23 Failed: 3)
  Failed tests:  5, 7, 9
/home/jiffin/qa/tools/pjd-fstest-20080816/tests/rename/00.t  (Wstat: 0 Tests: 79 Failed: 4)
  Failed tests:  49, 53, 57, 61

Th first tests(chown and open) when I tried manually they worked fine but via scripts they always fail even if I put sleep in the test case.
The third can be reproduced with following steps

1.) Create a file
2.) Check the ctime (c1)
3.) Rename the file
4.) Check ctime again (c2)
According posix behavior the c1 should be less than c2. But here both are same.
And after some time c2 changes (there is an delay I guess)

On FSAL_GLUSTER, the failure list (apart from above three) is kind of spurious.  All the failures are due to chown/chmod/truncate call(setattr). The effect of setattr is reflected only after some seconds. When put sufficient sleep most of the test got passed

Does FSAL_GLUSTER support nanosecond resolution timestamps? If not, anything trying to test mtime/ctime will likely fail.

I need to run pjd-fstests on FSAL_VFS sometime...

Oh, I should also note that I had to change some pjd-fstests to be aware of Ganesha in order to pass. See my github repo.

https://github.com/ffilz/pjdfstest

There's also a slightly different version of this suite, which I also have changes in:

https://github.com/ffilz/ntfs-3g-pjd-fstest

(In reply to Frank Filz from comment #6)
> Does FSAL_GLUSTER support nanosecond resolution timestamps? If not, anything

From the code, its seems to be gluster supports only microseconds. I am making necessary changes to check whether it will work or not

Thanks for the input Frank

> trying to test mtime/ctime will likely fail.
> 
> I need to run pjd-fstests on FSAL_VFS sometime...

There are some differences in what passes between NSF v3 and NFS v4...

I'm a bit surprised you haven't hit at least some of the things I made changes for.

What is your source for the tests? For the ntfs-3g-pjd-fstest version I do have a fix in chown/00.t

Hmm, at a quick look, that suite (which also mentions my repos) looks more like ntfs-3g-pjd-fstest, so my patch to chown/00.t might be applicable.

Could you get some details on the failures (it's been long enough that I forget how to get them...).

It would also be worth running against FSAL_VFS to see what differences there are.

If this is still an issue please open an issue in the github tracker at https://github.com/nfs-ganesha/nfs-ganesha/issues