Zpool status shows scrub date of Dec 31, 1969

UNIX Solaris
1

hello,
We are using Solaris 11.3 on SPARC T5-2. The below is the actual output from "zpool status" command. The disks were scrubed last week, but it says the scrub repaired on Dec 31, 1969.
Does anyone know how to correct this to report the correct date?
Thanks

  pool: rpool
 state: ONLINE
  scan: scrub repaired 0 in 25m24s with 0 errors on Wed Dec 31 19:00:00 1969

config:

        NAME        STATE     READ WRITE CKSUM
        rpool       ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            c1d0s0  ONLINE       0     0     0
            c1d2s0  ONLINE       0     0     0

errors: No known data errors

  pool: u02
 state: ONLINE
  scan: scrub repaired 0 in 21m44s with 0 errors on Wed Dec 31 19:00:00 1969

config:

        NAME      STATE     READ WRITE CKSUM
        u02       ONLINE       0     0     0
          c1d1s0  ONLINE       0     0     0
          c1d3s0  ONLINE       0     0     0
2

What is the output of date on that box ?

Regards
Peasant.

3

The server has the corrected time. The server is synced with time server every day.

This is Oracle SPARC VM domain. I wonder if this has anything to do with this.

---------- Post updated 05-02-17 at 04:32 AM ---------- Previous update was 05-01-17 at 02:36 PM ----------

The server already had correct time, but the zpool status still shows Dec 31, 1969.
Has any one encountered this issue before?

root@T520:~# date
Tuesday, May  2, 2017 04:30:50 AM EDT
root@T520:~# zpool status
  pool: rpool
 state: ONLINE
  scan: scrub repaired 0 in 4m16s with 0 errors on Wed Dec 31 19:00:00 1969

config:

        NAME                         STATE     READ WRITE CKSUM
        rpool                        ONLINE       0     0     0
          mirror-0                   ONLINE       0     0     0
            c0t5000CCA0707CED20d0s0  ONLINE       0     0     0
            c0t5000CCA0707CF380d0s0  ONLINE       0     0     0

errors: No known data errors

  pool: u01
 state: ONLINE
  scan: scrub repaired 0 in 20m17s with 0 errors on Wed Dec 31 19:00:00 1969

config:

        NAME                         STATE     READ WRITE CKSUM
        u01                          ONLINE       0     0     0
          mirror-0                   ONLINE       0     0     0
            c0t5000CCA0707CED20d0s3  ONLINE       0     0     0
            c0t5000CCA0707CF380d0s3  ONLINE       0     0     0
4

It looks like scrub cleared the counts and cleared the timestamp. Note that in the US Eastern timezone, the local time corresponding to the UNIX Epoch -- which is the time with timestamp 0 (midnight at the start of January 1, 1970 GMT) is Wed Dec 31 19:00:00 1969 EST.

5

zpool scrub/resilver timestamp is incorrect on SPARC systems running Solaris 11.3 (Doc ID 2131291.1)

Notice that this bug does not affect your system in any other way other then wrong display of timestamp in zpool commands.

You should update your system to Oracle Solaris 11.3.4.5.0 or greater.
Probably followed by a zpool upgrade for those pools (i cannot find info if that step is also required).

Notice that if you upgrade your rpool and pools, you will not be able to rollback to older release(s) via beadm .

Get your current release to verify :

pkg info entire

Execute that command on both hypervisor and LDOM.

Check out my oracle website for bug identification, workarounds and such.
You'll need an account and support for that server (to download patches as well).

Hope that helps
Regards
Peasant.

1 Like
6

Thank you very much for the answer.