Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.4.0, Lustre 2.4.1, Lustre 2.5.0
-
FSTYPE=zfs
-
3
-
9641
Description
We need improve posix.sh to support BASELINE_FS=zfs so as to compare the results with zfs.
Currently, running posix.sh on Lustre b2_4 build #29 with FSTYPE=zfs and BASELINE_FS=ext4 failed as follows:
FAILURE SUMMARY: POSIX failures: 21 Test Name Baseline Lustre Report access.37 Succeeded Unresolved chdir.6 Succeeded Unresolved chmod.11 Succeeded Unresolved chmod.5 Succeeded Unresolved chown.10 Succeeded Unresolved creat.24 Succeeded Failed fcntl.18 Succeeded Unresolved fcntl.35 Succeeded Unresolved fpathconf.8 Succeeded Failed link.16 Succeeded Unresolved mkdir.13 Succeeded Failed mkfifo.11 Succeeded Failed open.38 Succeeded Failed opendir.9 Succeeded Unresolved pathconf.10 Succeeded Failed pathconf.24 Succeeded Unresolved rename.26 Succeeded Unresolved rmdir.14 Succeeded Unresolved stat.8 Succeeded Unresolved unlink.13 Succeeded Unresolved utime.12 Succeeded Unresolved
Please refer to the Maloo report for FAILURE DESCRIPTIONS:
https://maloo.whamcloud.com/test_sets/6768b678-025b-11e3-b384-52540035b04c
Attachments
Activity
Patch for Lustre b2_4 branch to make posix.sh support BASELINE_FS=zfs is in http://review.whamcloud.com/8323.
Not sure if the other failures. It would be useful to file subtickets for the failures with the text from the failing tests.
Besides LU-3603, LU-4219 and LU-4220 were created to track the failures.
I think all of the pathconf failures may be caused by pathconf being hard coded in glibc based on the Filesystem magic number. That means it isn't possible to change the value for Lustre without recompiling glibc.
Not sure if the other failures. It would be useful to file subtickets for the failures with the text from the failing tests.
Patch for master branch to make posix.sh support BASELINE_FS=zfs is in http://review.whamcloud.com/8180.
After the patch is ready to land, it can also be cherry-picked to Lustre b2_4 branch.
After applying the above patch on Lustre b2_4 build #49, I manually ran posix test with FSTYPE=zfs and got the following test results:
https://maloo.whamcloud.com/test_sessions/e61c04ee-4634-11e3-810a-52540035b04c
News POSIX successes: 2 Test Name Baseline Lustre Report write.24 Failed Succeeded write.28 Failed Succeeded FAILURE SUMMARY: POSIX failures: 19 Test Name Baseline Lustre Report access.37 Succeeded Unresolved chdir.6 Succeeded Unresolved chmod.11 Succeeded Unresolved chmod.5 Succeeded Unresolved chown.10 Succeeded Unresolved creat.24 Succeeded Failed fpathconf.8 Succeeded Failed link.16 Succeeded Unresolved mkdir.13 Succeeded Failed mkfifo.11 Succeeded Failed open.38 Succeeded Failed opendir.9 Succeeded Unresolved pathconf.10 Succeeded Failed pathconf.24 Succeeded Unresolved rename.26 Succeeded Unresolved rmdir.14 Succeeded Unresolved stat.8 Succeeded Unresolved unlink.13 Succeeded Unresolved utime.12 Succeeded Unresolved
All of the "Unresolved" failures are LU-3603. I'll investigate the "Failed" failures.
Lustre build: http://build.whamcloud.com/job/lustre-b2_4/47/
Distro/Arch: RHEL6.4/x86_64
FSTYPE=zfs
The same failure occurred:
https://maloo.whamcloud.com/test_sets/98c845fc-43ac-11e3-942a-52540035b04c
Landed for 2.4.2 and 2.6. Will land for 2.5.1 shortly.