From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] more info on fossil crashes
Date: Mon, 14 Jul 2003 18:51:33 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0307141825160.29555-101000@fbsd.cpsc.ucalgary.ca> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1518 bytes --]
The little script attached in this email manages to crash my fossil server
with 100% reproducibility (i.e. 5 out of 5, I got sick of rebooting so I'm
not trying anymore).
The error message on the console is:
[heavy io]
disk: io=10000 at 0.991ms
assert failed: b->nlock == 1
fossil 44: suicide: sys: trap: fault read addr=0x0 pc=0x0002b5af
[here I usually reboot]
The machine does not panic, it simply becomes unusable.
The attachment: the attached archive includes a small program that I use to
extract subfonts from a .bdf font file. It's a modified version of Skip
Tavakkolian's bdf2subf. Also included is a sample .bdf file. The script
'runtest' will extract all glyphs from the .bdf file and save them in
files named according to the range the subfont covers; after the extraction
is complete the script will attempt to detele all subfont files and will
cause my fossil to crash.
Symptoms: I don't seem to lose any other data. Before deletion there are
5000+ files in the directory. After a reboot I usually find around 1600
still remaining.
Setup: I run fossil over a two-disk mirror using devfs, the disks it mirrors
to are 80GB Matrox IDE disks set up as sdC0 and sdD0, running with UDMA4.
Debugging: Had a brief look at /sys/src/cmd/fossil/cache.c (where the nlock
mangling occurs, the assert fails in disk.c) but the code looks like it's in
a working state still -- so here's reporting the error to those who know how
to fix it better than I do.
cheers, andrey
[-- Attachment #2.1: Type: text/plain, Size: 416 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: APPLICATION/X-GZIP; NAME="rmtest.tgz"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.44.0307141842000.29555@fbsd.cpsc.ucalgary.ca>
Content-Description:
Content-Disposition: ATTACHMENT; FILENAME="rmtest.tgz"
[-- Attachment #2.2: rmtest.tgz.suspect --]
[-- Type: application/octet-stream, Size: 488533 bytes --]
reply other threads:[~2003-07-15 0:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.44.0307141825160.29555-101000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).