From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cwfs(4) failing: phase error after recover or suicide
Date: Thu, 20 Sep 2007 20:03:43 -0400 [thread overview]
Message-ID: <361b9a60bbbfd6c2c7cdd1db52644d68@quanstro.net> (raw)
In-Reply-To: <509071940709201613v1a23ae8bk4afe671671ead735@mail.gmail.com>
> that was the first thing i checked. in acid, print(cwio:h) showed
> seemingly useful non-0 numbers. but apparently i wasn't paying very
> close attention: h in cwio is a Cache*, not a Cache, so i needed
> print(*cwio:h). yup, msize is zero.
>
> geoff's been providing suggestions and thinks that the recover didn't
> actually succeed, so i'm focusing on that case for now. more info as
> it presents.
that's what i guessed your problem was. (since msize just had to be zero.)
i would guess that your new fworm is not exactly the same (calculated)
size as your old worm. i think you can fix this by simply dropping the "f"
from your device string. this will inhibit the maintence of the bitmap
at the end of the fake worm.
anyway, what is the compelling reason to move to cwfs? i have been
spending a lot of time with it in the last 6 weeks. i've made some substantial
performance improvements. and i've added aoe.
- erik
next prev parent reply other threads:[~2007-09-21 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 22:28 [9fans] cwfs(4) failing: phase error after recover or suicide after normal startup Anthony Sorace
2007-09-18 23:13 ` erik quanstrom
2007-09-20 23:13 ` Anthony Sorace
2007-09-21 0:03 ` erik quanstrom [this message]
2007-09-21 1:53 ` [9fans] cwfs(4) failing: phase error after recover or suicide Anthony Sorace
2007-09-21 2:00 ` erik quanstrom
2007-09-21 3:10 ` Anthony Sorace
2007-09-21 3:39 ` 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=361b9a60bbbfd6c2c7cdd1db52644d68@quanstro.net \
--to=quanstro@quanstro.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).