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 01:54:16 -0700 [thread overview]
Message-ID: <200907290154.17195.corey@bitworthy.net> (raw)
In-Reply-To: <200907282124.01673.corey@bitworthy.net>
On Tuesday 28 July 2009 21:24:01 Corey wrote:
> On Tuesday 28 July 2009 18:42:05 Russ Cox wrote:
<snip>
> > It's not a question of time zones. Time zones don't matter.
> > It's just that the clock was wrong before and later is
> > correct--there are many reasons this might happen--
> > and venti shouldn't care.
> >
> > The time stamps, like the ones in a file system, are
> > informational. It's okay if they're wrong. There's no
> > need to print.
>
> The problem isn't confined to unnecessary warning messages
> being printed.
>
> What about the 'arena arenas00: header is out-of-date' error,
> and the subsequent re-indexing (on every reboot) which occurs
> as a result of the condition?
<snip>
I think now that the constant indexing on reboot I'm seeing is an
entirely different problem.
It seems very similar to this:
http://www.mail-archive.com/9fans@cse.psu.edu/msg16585.html
http://www.mail-archive.com/9fans@cse.psu.edu/msg16590.html
My standalone terminal is always doing the index, the problem seemed
to have just suddenly showed up for no reason - the system hasn't crashed,
I'm not doing anything 'weird', and I always run fshalt before shutting
down. And this persists across fresh installs.
It looks like I ran into two different problems at around the same
time.
next prev parent reply other threads:[~2009-07-29 8:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
[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
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
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=200907290154.17195.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).