From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 27 Jul 2009 14:56:59 -0600
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: corey@bitworthy.net, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <200907271331.55203.corey@bitworthy.net>
Message-ID: <alpine.BSF.2.00.0907271451220.50642@legolas.orthanc.ca>
References: <200907261803.53756.corey@bitworthy.net>
	<dd6fe68a0907270928p103021f8m8fdb0a07fdecc70e@mail.gmail.com>
	<200907271331.55203.corey@bitworthy.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last
 write time'
Topicbox-Message-UUID: 2f555930-ead5-11e9-9d60-3106f5b1d025

What does the BIOS setup screen say about the motherboard clock's idea of
the time? I suspect what's happening is the motherboard clock is set in
the future, you are formatting venti based on that time, and then later
firing up timesync which interprets the RTC as local time. If your RTC is
set to UTC and you're in the western hemisphere, the RTC clock will be
ahead of your local time.

The venti message spits out two ctime values IIRC. One is the timestamp
from when venti created the store, the other the block write time. date(1)
will decipher the values, and tell the true story.