On 26-Mar-09, at 8:36 PM, andrey mirtchovski wrote:
On Thu, Mar 26, 2009 at 1:27 PM, Eric Van Hensbergen
wrote:
I have VNC lite on my iphone, which amazingly isn't jailbroken...
-eric
sure, but that's a client. i thought you were talking about exporting
iPhone's screen and interfaces a
sorry if this is a dupe. my original reply seems to
have gone missing due to a local mishap.
> venti/read should be doing this check automatically since libventi/client.c
> builds with "int ventidoublechecksha1 = 1;" by default.
yet you're reporting that fossil thinks the score does not
match.
On Sat, Mar 28, 2009 at 01:31:01PM -0400, erik quanstrom wrote:
> it would be interesting to know if the score
> of the block returned by venti/read is correct.
venti/read should be doing this check automatically since libventi/client.c
builds with "int ventidoublechecksha1 = 1;" by default.
--nw
> AFAIK the disk is doing just fine. Moreover, even during the period when
> fossil is complaining, venti/read on 9fs's score works just fine. So I
> don't believe the fault is venti's.
i don't believe that conclusion is warranted.
/sys/src/cmd/fossil/cache.c:683,684
is where this condition gets
On Sat, Mar 28, 2009 at 11:11:25AM +, Charles Forsyth wrote:
> i've seen that just recently, but thought it might have been
> a failing (very old) drive, or a power failure beyond the endurance of the
> UPS.
> if neither of those are true in your case, it might be worth a deeper look.
> i also
On Sat Mar 28 06:54:35 EDT 2009, fors...@terzarima.net wrote:
> i've seen that just recently, but thought it might have been
> a failing (very old) drive, or a power failure beyond the endurance of the
> UPS.
> if neither of those are true in your case, it might be worth a deeper look.
> i also fo
This is likely too large a hammer, but when this happens I rebuild the
venti index
so that I can get past the issue. I see this more under Plan 9 than p9p. The
block in error always exists in an arena and a checkarenas reports no errors.
The problem usually persists across reboots until I reconst
i've seen that just recently, but thought it might have been
a failing (very old) drive, or a power failure beyond the endurance of the UPS.
if neither of those are true in your case, it might be worth a deeper look.
i also found there is a persistent problem that `check fix' won't fix.
(since it's
