9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'
Date: Wed, 29 Jul 2009 15:02:01 +0100	[thread overview]
Message-ID: <2564cf28c88b19176fe4108a2f0ce00e@quintile.net> (raw)
In-Reply-To: <200907290154.17195.corey@bitworthy.net>

> 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.

Not sure what you mean by "doing the index".

When you install you will have an empty venti and a full fossil.
on the next reboot the whole of fossil will be dumped to venti.
This first dump can take a long time (some hours). After this dumps
only take (typicially) a few secconds as only changed blocks are written.

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 (not sure if it starts again from
the begining or just from where it left off).

Perhaps this could be the "doing the index"? if so, try just leaving it
rattling overnight and then fshalt the next morning and it may come back
happy the next day.

Beware: shutting down during a dump is a bit unfriendly even if you did
an fshalt, it may be worth running a "venti check" check on fossil -
see fossilcons(8) - this is another very slow process I'am afraid.

-Steve



  reply	other threads:[~2009-07-29 14:02 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
2009-07-29 14:02                 ` Steve Simon [this message]
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=2564cf28c88b19176fe4108a2f0ce00e@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    --cc=corey@bitworthy.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).