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

On Monday 27 July 2009 13:38:58 erik quanstrom wrote:
> > each time using the same process/steps) - and now it doesn't go away,
> > even on a completely fresh install, even after I wiped the drives
> > completely.
>
> what's your disk wiping procdure?
>

I reboot with a gentoo linux rescue cd.

I run the following.

shred -zvun 1 /dev/hda1 # wipe data, zero out (takes about 90 minutes)

dd if=/dev/zero of=/dev/hda bs=512 count=1 # clear mbr

Then I delete the org plan 9 partition (/dev/hda1; i.e. /dev/sdC0) using fdisk

Finally, I reboot with the same plan 9 install cd I've been using, and
go through the standard install using fossil+venti


Then, after the install:

Log into system for first time as glenda; everything apparently ok at
this point.

But, when I fshalt, then reboot - at that point, the second login into the
machine, is when I start seeing the venti described venti errors.

I have repeated the above steps three times now, and have confidently
determined that the condition is persistent, and repeatable.

I'm also fairly certain that I'm not doing anything 'wierd', and there has
been no change in hardware or behavior of the machine throughout the
entire time I've been experimenting.



> > Now, every time I install plan 9 on this machine, even when I don't
> > change the clock or timezone in any way, it ends up with this issue where
> > venti complains about 'arenas00: header is out-of-date', then indexes
> > clumps, then starts rolling out those 'creation time after last write
> > time' messages. I have confirmed and verified this continues even after
> > multiple attempts at a 100% prestine re-install.
> >
> > Any ideas what could be the cause?  I wouldn't care quite so much if it
> > was just some sort of fluke that was remedied after another clean install
> > - but it's persisting even after I totally wipe the drive (using dd and
> > shred from a linux recovery disk), delete the partition table, and start
> > from scratch.
>
> motherboard battery dead?
>

Nope, I checked that after the second time I hit the issue all over again; and
verified the cmos time is correct.


> as long as you're editing venti
> source, you could print out both dates.  that would give a
> better picture of what's really going on.
>

Ok, I'll try this next.


Cheers