From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] More Fossil anomalies
Date: Sat, 21 Jun 2003 10:06:59 +0200 [thread overview]
Message-ID: <e33928cece8e1562326fecf60c3e0cb4@proxima.alt.za> (raw)
I think I'm moderately up to date, but I with all my commuting, I'm
having trouble keeping track. Is there an easy place to query the
Fossil version? A 'what' type ID?
I get, on my experimental system (thanks again, John!):
err2: decompression failed: offset out of range: off=5720 d=4331 nbits=13
disk: io=10005 at 9.805ms
err2: decompression gave partial block: 8186/8192
disk: io-10002 at 9.936ms
which sound quite ominous to me. Given that these are coincidental
with link problems raised here, I wonder if I have a broken Fossil and
how I should go about checking this. I think the host I'm running
Fossil on is a bit limited, memory wise, but I would wish for clearer
diagnostics.
++L
next reply other threads:[~2003-06-21 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 8:06 lucio [this message]
2003-06-21 9:42 ` Lucio De Re
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=e33928cece8e1562326fecf60c3e0cb4@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).