From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: corey@bitworthy.net,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'
Date: Mon, 27 Jul 2009 14:56:59 -0600 [thread overview]
Message-ID: <alpine.BSF.2.00.0907271451220.50642@legolas.orthanc.ca> (raw)
In-Reply-To: <200907271331.55203.corey@bitworthy.net>
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.
next prev parent reply other threads:[~2009-07-27 20:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 1:03 Corey
2009-07-27 16:28 ` Russ Cox
2009-07-27 20:31 ` Corey
2009-07-27 20:38 ` erik quanstrom
2009-07-27 20:58 ` Corey
2009-07-27 22:49 ` Corey
2009-07-27 22:52 ` erik quanstrom
2009-07-27 20:56 ` Lyndon Nerenberg [this message]
2009-07-30 4:15 ` Corey
[not found] <26a2b1a9fb6ec5947c440b48b8bde174@quanstro.net>
2009-07-27 23:56 ` Corey
2009-07-28 0:35 ` erik quanstrom
2009-07-28 8:52 ` Steve Simon
[not found] <664879e97485933b3ca1bc9e37760730@quanstro.net>
2009-07-28 5:05 ` Corey
2009-07-28 13:22 ` erik quanstrom
2009-07-28 15:16 ` Russ Cox
2009-07-28 22:14 ` Dave Eckhardt
2009-07-28 22:16 ` erik quanstrom
2009-07-28 22:56 ` Corey
2009-07-29 1:42 ` Russ Cox
2009-07-29 4:24 ` Corey
2009-07-29 8:54 ` Corey
2009-07-29 14:02 ` Steve Simon
2009-07-29 14:48 ` Russ Cox
2009-07-28 22:42 ` Corey
2009-07-28 23:50 ` erik quanstrom
[not found] <09c88626d985457ecaa621715f4f1af0@quanstro.net>
2009-07-29 0:42 ` Corey
2009-07-29 1:04 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.00.0907271451220.50642@legolas.orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).