From: Joshua Wood <josh@utopian.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti wrarena i/o errors
Date: Thu, 29 Nov 2007 04:12:58 -0800 [thread overview]
Message-ID: <9AC90B7C-FEE5-4FA0-A60A-6049CE79E322@utopian.net> (raw)
>
> The new machine is a VIA. I will try again without dma.
Were you manually turning dma on? If not, this is not likely to be a
case where your problem was same as the one I mentioned. I was
forcing dma on a chipset not listed in the distributed /sys/src/9/pc/
sdata.c.
> I will also
> add in the bloom partition, but I'm low on memory at the moment (256MB
> doesn't sound low to me, but I find the new venti can be a bit greedy
> if not constrained), so I'm not sure if that is actually worth doing.
It's optional, and it's not causing your problem, so I don't want to
distract from the immediate issue, but you can kinda get the best of
both worlds if memory is tight by starting with a bloom filter, then
dropping it from your venti conf as the system ages toward less write-
intensiveness.
> I will read the venti man pages more slowly to understand better.
sources/contrib/steve/doc/Venti-rescue.pdf is a mildly-dated but
excellent supplement to the manual for the task you're attempting,
and discusses memory allotment between venti and fossil in an
appendix, too.
--
Josh
next reply other threads:[~2007-11-29 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 12:12 Joshua Wood [this message]
2007-12-04 23:02 ` Robert Raschke
2007-12-05 0:29 ` Russ Cox
[not found] <24c8b3ca4a8c192c1731e5e67d43f50a@tombob.com>
2007-12-06 9:54 ` Robert Raschke
2007-12-11 9:41 ` Robert Raschke
2007-12-14 0:45 ` sqweek
2007-12-14 0:48 ` ron minnich
2007-12-14 8:22 ` Christian Kellermann
2007-12-14 16:05 ` ron minnich
2007-12-14 15:18 ` Richard Miller
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 17:44 Joshua Wood
2007-11-29 1:11 Joshua Wood
2007-11-29 9:30 ` Robert Raschke
2007-11-28 22:42 Robert Raschke
2007-11-28 23:29 ` 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=9AC90B7C-FEE5-4FA0-A60A-6049CE79E322@utopian.net \
--to=josh@utopian.net \
--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).