[LU-5977] Remove correction for bad timestamp Created: 03/Dec/14 Updated: 03/Sep/15 Resolved: 03/Sep/15 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.8.0 |
| Fix Version/s: | Lustre 2.8.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | Bob Glossman (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | easy, patch | ||
| Issue Links: |
|
||||||||||||
| Severity: | 3 | ||||||||||||
| Rank (Obsolete): | 16690 | ||||||||||||
| Description |
|
There was a bug in Lustre 2.1.0 that caused negative timestamps. In Lustre 2.8, tag 2.7.53 and above, code to correct for bad timestamps in Lustre 2.1.0 will no longer be used. In lustre/include/dt_object.h: #define LU221_BAD_TIME (0x80000000U + 24 * 3600) In lustre/ofd/ofd_objects.c routine ofd_attr_get(), #if LUSTRE_VERSION_CODE < OBD_OCD_VERSION(2, 7, 53, 0) /* Try to correct for a bug in 2.1.0 (LU-221) that caused * negative timestamps to appear to be in the far future, * due old timestamp being stored on disk as an unsigned value. * This fixes up any bad values stored on disk before * returning them to the client, and ensures any timestamp * updates are correct. LU-1042 */ if (unlikely(la->la_atime == LU221_BAD_TIME)) la->la_atime = 0; if (unlikely(la->la_mtime == LU221_BAD_TIME)) la->la_mtime = 0; if (unlikely(la->la_ctime == LU221_BAD_TIME)) la->la_ctime = 0; #endif |
| Comments |
| Comment by Gerrit Updater [ 25/Aug/15 ] |
|
Giuseppe Di Natale (dinatale2@llnl.gov) uploaded a new patch: http://review.whamcloud.com/16077 |
| Comment by Gerrit Updater [ 03/Sep/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/16077/ |
| Comment by Joseph Gmitter (Inactive) [ 03/Sep/15 ] |
|
Landed for 2.8. |