Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Lustre 1.8.6
-
None
-
Lustre Branch: v1_8_6_RC2
Lustre Build: http://newbuild.whamcloud.com/job/lustre-b1_8/80/
e2fsprogs Build: http://newbuild.whamcloud.com/job/e2fsprogs-master/40/
Distro/Arch: RHEL6/x86_64(patchless client, in-kernel OFED, kernel version: 2.6.32-131.2.1.el6)
RHEL5/x86_64(server, OFED 1.5.3.1, kernel version: 2.6.18-238.12.1.el5_lustre)
Lustre Branch: v1_8_6_RC2 Lustre Build: http://newbuild.whamcloud.com/job/lustre-b1_8/80/ e2fsprogs Build: http://newbuild.whamcloud.com/job/e2fsprogs-master/40/ Distro/Arch: RHEL6/x86_64(patchless client, in-kernel OFED, kernel version: 2.6.32-131.2.1.el6) RHEL5/x86_64(server, OFED 1.5.3.1, kernel version: 2.6.18-238.12.1.el5_lustre)
-
3
-
18,169
-
4068
Description
sanityn test 4 failed as follows:
== test 4: fstat validation on multiple mount points ========== == 05:07:34 Mtimes don't match 1308053256, 1308068405 sanityn test_4: @@@@@@ FAIL: test_4 failed with 1
Maloo report: https://maloo.whamcloud.com/test_sets/7209239a-96f3-11e0-9a27-52540025f9af
This is caused by the mismatched clocks between the client and server nodes:
$ pdsh -l root -S -w client-[10,12],fat-amd-[1-2] date client-10: Tue Jun 14 12:43:33 PDT 2011 client-12: Tue Jun 14 12:43:44 PDT 2011 fat-amd-1: Tue Jun 14 19:43:29 PDT 2011 fat-amd-2: Tue Jun 14 19:43:28 PDT 2011
However, per the comments from Andreas in bug 18169:
This should work correctly so should be investigated, but isn't a release blocking problem.
Attachments
Issue Links
- Trackbacks
-
Lustre 1.8.x known issues tracker
While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA