From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <361b9a60bbbfd6c2c7cdd1db52644d68@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cwfs(4) failing: phase error after recover or suicide
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 20 Sep 2007 20:03:43 -0400
In-Reply-To: <509071940709201613v1a23ae8bk4afe671671ead735@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: c1e682d6-ead2-11e9-9d60-3106f5b1d025

> 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