9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'
Date: Mon, 27 Jul 2009 13:58:02 -0700	[thread overview]
Message-ID: <200907271358.02882.corey@bitworthy.net> (raw)
In-Reply-To: <c887ecca7c004fff04ac254a3e7d4fa1@coraid.com>

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






  reply	other threads:[~2009-07-27 20:58 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 [this message]
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
     [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=200907271358.02882.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).