From mboxrd@z Thu Jan  1 00:00:00 1970
From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Date: Wed, 29 Jul 2009 21:15:44 -0700
User-Agent: KMail/1.11.4 (Linux/2.6.27-gentoo-r8; KDE/4.2.4; i686; ; )
References: <200907261803.53756.corey@bitworthy.net>
In-Reply-To: <200907261803.53756.corey@bitworthy.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907292115.44517.corey@bitworthy.net>
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last
	write time'
Topicbox-Message-UUID: 31c3532a-ead5-11e9-9d60-3106f5b1d025

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
>