On 2010-02-25, at 22:52, Satoshi Isono wrote: > Thank you for your opinion. > You means I should do version up on client. Does it mean from 1.6.5 > to 1.6.6? By which version is it fixed?
I would suggest 1.8.2, which is the most recent release. > And could you do test using my script and report me with output? sh check.sh ## START ORIGINAL TIME STAMP mv_test.txt 277980 2010-02-25 23:34:11.000000000 mv_test.txt.org 279316 2010-02-25 23:34:11.000000000 ## REVISE mv_test.txt ## CHECK TIME STAMP mv_test.txt 277980 2010-02-25 23:34:48.000000000 mv_test.txt.org 279316 2010-02-25 23:34:11.000000000 You are free to look through the lustre/ChangeLog to see which bug(s) contained fixes for this problem, but the above shows it is at least fixed in 1.8.2. > At 10/02/26（金）13:25, Andreas Dilger wrote: >> On 2010-02-25, at 20:17, Satoshi Isono wrote: >>> I got the strange output on mtime information. Does anyone have such >>> experiences? Could you try to do this test, please? >>> My Lustre environment is that client: 1.6.5.1-2.6.18_53.1.6.el5 and >>> OSS: 1.6.6.-2.6.18_92.1.10.el5. >> >> >> I suggest that you upgrade to a newer version of Lustre. There >> were a >> number of mtime fixes, along with hundreds of other bug fixes since >> 1.6.5. >> >> Cheers, Andreas >> -- >> Andreas Dilger >> Sr. Staff Engineer, Lustre Group >> Sun Microsystems of Canada, Inc. > > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
