From: Vester Thacker <vester.thacker@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] venti i/o error
Date: Mon, 9 May 2005 22:11:45 +0900 [thread overview]
Message-ID: <32a656c205050906114d9d3a72@mail.gmail.com> (raw)
I am installing Plan 9 to an AMD64 machine with a 250GB drive and
chose the fossil+venti option. After a successful installation and
reboot, I modified the fossil.conf file, to allow me
to continue the server configuration, as such:
fsys main open -AWP -V -c 3000
After modifying fossil.conf as mentioned in the wiki, I rebooted the
machine. But during the next bootstrap I received the following:
Plan9
cpu0: 2002MHz AuthenticAMD AMD64 (cpuid: AX 0x0FC0 DX 0x78BFBFF)
ELCR: 0E20
pcirouting: ignoring south bridge PCI.0.17.0 1106/3227
miistatus 2
#l0: rhine: 100Mbps port 0xEC00 irq 10: 000129FFBF0F
38944 free pages, 155776K bytes, 592576K swap
root is from (tcp, il, local) [local!#S/sdC0/fossil]: <enter>
user[none]: <glenda>
time...
venti...err 2: arena creation time after last write time
fossil (#S/sdC0/fossil)...version...time...
boot: /386/init: venit i/o error block c64f724407b2ee42d5efc65c99bca77b0fe708bb:
not connected to venti server
panic: boot process died: unknown
dumpstack disabled
cpu0: exiting
What is causing this to occur? Is there something I need to do
beforehand that would prevent this error from occurring?
Thanks in advance.
-vester
next reply other threads:[~2005-05-09 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 13:11 Vester Thacker [this message]
2005-05-09 13:33 ` [9fans] " Vester Thacker
-- strict thread matches above, loose matches on Subject: below --
2004-10-18 4:52 [9fans] nsf funding research into better (operating) systems Martin C.Atkins
2004-10-18 7:00 ` Skip Tavakkolian
2004-10-18 7:40 ` Martin C.Atkins
2004-10-29 2:01 ` [9fans] venti i/o error arisawa
2004-10-29 4:37 ` arisawa
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=32a656c205050906114d9d3a72@mail.gmail.com \
--to=vester.thacker@gmail.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).