[LU-380] POSIX: write.15: time stamps incorrect: mtime, ctime were not updated Created: 31/May/11 Updated: 27/Sep/16 Resolved: 27/Sep/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.1.0, Lustre 2.1.1, Lustre 2.1.2, Lustre 1.8.8, Lustre 1.8.7, Lustre 1.8.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jian Yu | Assignee: | WC Triage |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Lustre Branch: b1_8 |
||
| Severity: | 3 |
| Bugzilla ID: | 23,300 |
| Rank (Obsolete): | 10175 |
| Description |
|
Here is the result of running the LSB-VSX POSIX test suite (lts_vsx-pcts2.0beta2.tgz): The baseline is ext4. #################################################### Test Name: write.15 Failed Test Description: The time fields st_ctime and st_mtime are marked for update by a call write(). Posix Ref: Component WRITE Assertion 6.4.2.2-25(A) Test Strategy: CREATE new file using creat() SAVE timestamps using savtimes() - (genlib) WRITE MSG_LEN bytes to file VERIFY that st_ctime and st_mtime have been updated using chktimes() - (genlib) CLOSE file descriptor using close() UNLINK file REPEAT for FIFO and pipe: SAVE timestamps using savtimes()/fsavtimes() - (genlib) WRITE MSG_LEN bytes to file VERIFY that st_ctime and st_mtime have been updated using chktimes()/fchktimes() - (genlib) Test Information: time stamps incorrect: mtime, ctime were not updated |
| Comments |
| Comment by Jian Yu [ 17/Jun/11 ] |
|
Lustre Branch: v1_8_6_RC2 POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/2cd4d244-98d1-11e0-9a27-52540025f9af The baseline is ext4. |
| Comment by Jian Yu [ 18/Jul/11 ] |
|
Lustre Tag: v2_0_65_0 POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/e4ede34c-b13c-11e0-b33f-52540025f9af The baseline is ext4. Test unlink.6 failed as follows: #################################################### Test Name: unlink.6 Failed Test Description: A successful call to unlink() marks for update the st_ctime and the st_mtime field of the parent directory. When the file's link count does not become zero after a successful call to unlink(), the st_ctime field of the file is marked for update. Posix Ref: Component UNLINK Assertion 5.5.1.2-30(A) Posix Ref: Component UNLINK Assertion 5.5.1.2-31(A) Test Strategy: FOR an ordinary file and a FIFO (when not testing XNFS) CREATE file using creat() or mkfifo() CLOSE file using close() CREATE link to directory using link() OBTAIN file status information using stat() for the parent directory SAVE times stamps using savtimes() - (genlib) UNLINK link using unlink() VERIFY that unlink() returned 0 VERIFY that the link no longer exists using eaccess() - (genlib) VERIFY that st_ctime has been updated using chktimes() OBTAIN file status information using stat() for the parent directory VERIFY that the st_ctime and st_mtime of the parent directory have changed UNLINK file using unlink() Test Information: remaining link time stamps incorrect: ctime was not updated remaining link time stamps incorrect: ctime was not updated #################################################### |
| Comment by Jian Yu [ 25/Aug/11 ] |
|
Lustre Tag: v2_1_0_0_RC1 POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/0aaa9fba-cefe-11e0-8d02-52540025f9af The baseline is ext4. |
| Comment by Jian Yu [ 11/Oct/11 ] |
|
Lustre Tag: v1_8_7_WC1_RC1 POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/30866dc0-f3ef-11e0-908b-52540025f9af The baseline is ext4. |
| Comment by Jian Yu [ 13/Feb/12 ] |
|
Lustre Tag: v2_1_1_0_RC2 POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/ffbf6c1c-5629-11e1-af68-5254004bbbd3 The baseline is ext4. |
| Comment by Jian Yu [ 11/May/12 ] |
|
Lustre Tag: v1_8_8_WC1_RC1 POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/99712946-9b2a-11e1-a0a0-52540035b04c The baseline is ext4. |
| Comment by Jian Yu [ 30/May/12 ] |
|
Lustre Tag: v2_1_2_RC2 The same issue occurred: https://maloo.whamcloud.com/test_sets/a50bad22-a993-11e1-9ad2-52540035b04c |
| Comment by Jian Yu [ 07/Aug/12 ] |
|
Comment from Vladimir V. Saveliev in Bugzilla 23300: |
| Comment by Jian Yu [ 07/Aug/12 ] |
|
After updating the LSB-VSX POSIX test suite to disable FIFO test in write.15 and unlink.6, Lustre POSIX compliance testing passed on T.write and T.unlink test sets (baseline is ext4): Lustre branch: master |
| Comment by Andreas Dilger [ 27/Sep/16 ] |
|
Closing this old ticket. |