My Oracle Support Banner

Time-Date Stamps Being Reported by 'ls -l' is Inconsistent Across Nodes on OCFS2 File System (Doc ID 605188.1)

Last updated on AUGUST 04, 2018

Applies to:

Linux Kernel - Version: 1.2.3
This problem can occur on any platform.

Symptoms

Files on one of the OCFS2 file systems are not reflecting the correct date/time stamp, for example:

DEV1:
$ hostname
cosxaor0e.amcastle.com
$ pwd
/d13/oradev/devdata
$ ls -ltr redo*
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr15a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr15b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr16a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr16b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr17a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr17b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr18a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:55 redo_th2_gr18b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:08 redo_th1_gr11a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:08 redo_th1_gr11b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:26 redo_th1_gr12a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:26 redo_th1_gr12b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:50 redo_th1_gr13a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:50 redo_th1_gr13b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:56 redo_th1_gr10b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:56 redo_th1_gr10a.dbf
$

DEV2:
$ hostname
cosxaor0f.amcastle.com
$ pwd
/d13/oradev/devdata
$ ls -ltr redo*
-rw-r-----  1 oradev dba 52429312 Nov 11 01:56 redo_th1_gr11a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:56 redo_th1_gr11b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:58 redo_th1_gr12b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 01:58 redo_th1_gr12a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 02:04 redo_th1_gr13a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 02:04 redo_th1_gr13b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 02:08 redo_th1_gr10a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 11 02:08 redo_th1_gr10b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 11:00 redo_th2_gr16a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 11:00 redo_th2_gr16b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 11:39 redo_th2_gr17a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 11:39 redo_th2_gr17b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:26 redo_th2_gr18b.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:26 redo_th2_gr18a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:57 redo_th2_gr15a.dbf
-rw-r-----  1 oradev dba 52429312 Nov 29 12:57 redo_th2_gr15b.dbf
$

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Symptoms
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.