9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] More venti sync woes.
Date: Thu, 27 Sep 2007 17:53:30 -0400	[thread overview]
Message-ID: <ee9e417a0709271453q4f599031v248ce951957edb84@mail.gmail.com> (raw)
In-Reply-To: <509071940709261232t1046ecv2ce6800d549c180c@mail.gmail.com>

i don't understand what printed sync... - venti or fossil?

boot from a boot cd and then run venti/venti -c config
by hand, and then you can run ps and acid to see what
it is spending its time doing.

i half-doubt that venti is actually the one sitting around.
it could be that fossil is trying to write the initial set of
blocks out to venti, and that that's what is taking a while.
but booting from a cd and being able to run ps, etc.
will tell you for sure.

finally, don't underestimate the slowness of non-dma disk.
venti is *very* disk-intensive.  i was measuring some
changes i had made to venti recently and was very surprised
that i was only getting under 1MB/s, and then i realized
that dma was off.  it matters.

what's your venti config?

russ


  parent reply	other threads:[~2007-09-27 21:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 19:32 Anthony Sorace
2007-09-26 19:39 ` Steve Simon
2007-09-26 19:41   ` erik quanstrom
2007-09-26 19:49     ` Anthony Sorace
2007-09-27 21:53 ` Russ Cox [this message]
2007-09-27 22:49   ` Anthony Sorace
2007-09-27 23:03     ` erik quanstrom
2007-09-28  3:16     ` Russ Cox
2007-09-28  9:01       ` Kernel Panic
2007-09-28 16:35         ` Anthony Sorace
2007-09-27 23:54   ` Charles Forsyth
2007-09-28  0:10     ` erik quanstrom
2007-09-28  0:19       ` Charles Forsyth
2007-09-28  0:19         ` erik quanstrom
2007-09-28  4:01       ` Bruce Ellis

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=ee9e417a0709271453q4f599031v248ce951957edb84@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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).