From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'
Date: Wed, 29 Jul 2009 21:15:44 -0700 [thread overview]
Message-ID: <200907292115.44517.corey@bitworthy.net> (raw)
In-Reply-To: <200907261803.53756.corey@bitworthy.net>
On Tuesday 28 July 2009 17:42:23 Corey wrote:
> My experience is indicating a different reality,
> or I'm still not interpreting my experience correctly.
>
It was definitely the latter.
On Tuesday 28 July 2009 16:50:15 erik quanstrom wrote:
> you should note that this has absolutely zero to do with
> timesync, the bios clock or tea in china. this changes the
> human readable time only. fossil and venti just don't care.
>
On Wednesday 29 July 2009 07:48:54 Russ Cox wrote:
> The fact that this is happening repeatedly suggests
> that fossil is trying to do a dump to venti but you are not
> leaving the machine up long enough that it can complete,
> so every time you reboot, it starts writing blocks to venti
> again, causing new indexing work that doesn't finish before
> you reboot again.
>
On Wednesday 29 July 2009 07:02:01 Steve Simon wrote:
> Is it possible that you did not let this intiial dump finish when
> you first rebooted your machine. In that case each time you reboot
> it will be trying to continue this dump
>
Erik, Russ and Steve - thanks a ton for sticking with me on that;
and for explaining things so well. Very much appreciated.
Quick summary of what went wrong for me there:
It's exactly as Russ and Steve described - at some point I began
rebooting the terminal before fossil had finished dumping to venti.
The reason I became so confused was because prior to that, I had
been leaving my terminal up for long periods between reboots. It
wasn't until I first attempted to change the timezone that I _also_
began rebooting my terminal soon after the first-time login after
an install had completed. I was ignorant of how fossil+venti
interacted, and I had not yet experienced the results of rebooting
before the dump had completed - so I fixated on the timezone as
the only thing that seemed to be connected to the "problem" I was
seeing - and the 'creation time after last write time' error from venti
was an additional red-herring.
Thanks again for helping me along guys, and to Russ for providing
such an in depth look into what I was missing regarding fossil+venti;
way cool!
Respectfully,
Corey
On Sunday 26 July 2009 18:03:53 Corey wrote:
> The following is being printed to the console non-stop:
>
> err 2: arena arenas00 creation time after last write time
>
>
> ... and I saw this during bootup:
>
> arena arenas00: header is out-of-date
>
>
> Apparently my clock/date was set a day ahead when I installed the terminal.
>
> How do I correct the situation?
>
> I searched around, but only found one other post regarding this problem,
> but I did not see a solution in that thread:
>
> http://www.mail-archive.com/9fans@cse.psu.edu/msg08167.html
>
next prev parent reply other threads:[~2009-07-30 4:15 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
2009-07-30 4:15 ` Corey [this message]
[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=200907292115.44517.corey@bitworthy.net \
--to=corey@bitworthy.net \
--cc=9fans@9fans.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).