From: Sam Ducksworth <sam@ducksworth.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] worm problems
Date: Sun, 9 Dec 2001 07:47:22 -0600 [thread overview]
Message-ID: <Pine.BSF.4.33.0112090719160.79065-100000@lucifer.ducksworth.com> (raw)
hello all,
i noticed this morning that my fileserver was caught in a reboot cycle.
each time it comes up everything looks normal until just before it
displays the fs console prompt.
here is what it prints:
fworm: read 5
WORM SUPER BLOCK READ FAILED
0 0 fs:
then lots of disk activity followed by the fileserver panicing and
vomiting on the screen and then rebooting. i was able to stop the reboot
cycle by issuing the following command:
0 0 fs: cwcmd startdump 0
that got me back so i can at least use the file server. i also verified
the problem by issuing the following command:
0 0 fs: cwcmd touchsb
fworm: read 5
WORM SUPER BLOCK READ FAILED
any ideas on how to fix this one? BTW this is a pseudo worm setup.
--sam
next reply other threads:[~2001-12-09 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 13:47 Sam Ducksworth [this message]
2001-12-09 17:45 Russ Cox
2001-12-09 19:44 ` Sam Ducksworth
2001-12-09 22:03 Russ Cox
2001-12-09 23:52 ` Sam Ducksworth
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.BSF.4.33.0112090719160.79065-100000@lucifer.ducksworth.com \
--to=sam@ducksworth.com \
--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).