From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i/o error: wrenwrite
Date: Wed, 3 Mar 2004 09:34:31 +0100 [thread overview]
Message-ID: <503d190cb9a4472806f90bd0fdde7772@plan9.escet.urjc.es> (raw)
In-Reply-To: <200403030822.i238MZBg097480@adat.davidashen.net>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
I am not a hardware expert either. Wren was the name for the disk
device in fs(8), and I think kfs inherited the name. It refers to a rw
disk or partition. The messages can be understood AFAIK as I/O errors,
which usually correspond to broken hardware.
Regarding 2, I don't know how that may be.
Regarding 3, I know disks that do automatically what time ago you did
by hand (declaring some blocks as defects and instructing the disk to use
other spare ones instead). The only reason I may find for this is that your disk
detected an error and was able to correct it; but I'm not a hardware expert
either.
A power failure may cause all this depending on the disk you use, because it
may lead to broken disks (although I admit I've not seen this since long ago).
We use Plan 9 here for daily work: It runs a lab for students, our accounts,
we write programs and documents on it, read mail, etc. I indeed can say
that it's more reliable than Linux, according to my experience (that can be
different for others, of course). So I'd not be scared to use plan 9 for daily
work; I'd be to switch back to what I used before.
If I may help somehow, let me know.
[-- Attachment #2: Type: message/rfc822, Size: 2852 bytes --]
From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i/o error: wrenwrite
Date: Wed, 3 Mar 2004 12:22:35 +0400 (AMT)
Message-ID: <200403030822.i238MZBg097480@adat.davidashen.net>
>
> Perhaps your disk recovered your bad blocks using spare ones and
> now there's no problem at all.
>
1) what exactly does the word mean?
2) how it depends on rebooting it from a different media?
3) among the messages displayed last time there was one that
it cannot open /adm/timezone/local. After the reboot, /adm/timezone/local
is where it should and unchanged (that is, my timezone as I put
it there).
Can it be something with controller state not properly initialized?
How exactly should I report my hardware configuration?
Why it only happens after a power failure and not during normal work,
if it is a hardware problem?
I am not a hardware expert. I am just trying to port some programs
to Plan9, and use it as a platform -- it was said to be 'finished',
that is, usable for work, and I hope it is mature indeed.
David Tolpin
next prev parent reply other threads:[~2004-03-03 8:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 7:57 David Tolpin
2004-03-03 8:06 ` Fco.J.Ballesteros
2004-03-03 8:10 ` David Tolpin
2004-03-03 8:15 ` Fco.J.Ballesteros
2004-03-03 8:22 ` David Tolpin
2004-03-03 8:34 ` Fco.J.Ballesteros [this message]
2004-03-03 8:59 ` David Tolpin
2004-03-03 9:51 ` Geoff Collyer
2004-03-03 9:54 ` David Tolpin
2004-03-03 10:39 ` matt
2004-03-03 10:43 ` David Tolpin
2004-03-03 11:37 ` Charles Forsyth
2004-03-03 12:19 ` David Tolpin
2004-03-03 12:46 ` boyd, rounin
2004-03-03 12:44 ` boyd, rounin
2004-03-03 20:35 ` splite
2004-03-03 21:25 ` Geoff Collyer
2004-03-03 21:42 ` splite
2004-03-03 22:48 ` boyd, rounin
2004-03-03 9:55 ` Bruce Ellis
2004-03-03 10:00 ` David Tolpin
2004-03-03 10:47 ` Richard Miller
2004-03-03 11:19 ` David Tolpin
2004-03-03 11:25 ` lucio
2004-03-03 11:34 ` David Tolpin
2004-03-03 20:11 ` splite
2004-03-03 20:25 ` David Tolpin
2004-03-03 13:41 ` jmk
2004-03-03 13:45 ` David Tolpin
2004-03-03 13:58 ` C H Forsyth
2004-03-03 13:58 ` lucio
2004-03-03 14:07 ` C H Forsyth
2004-03-03 14:04 ` David Tolpin
2004-03-03 14:14 ` lucio
2004-03-03 14:23 ` jmk
2004-03-03 14:24 ` David Tolpin
2004-03-03 21:34 ` Exact Eios " David Tolpin
2004-03-03 14:41 ` Derek Fawcus
2004-03-03 9:15 ` Richard Miller
2004-03-03 9:18 ` David Tolpin
2004-03-03 12:31 ` boyd, rounin
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=503d190cb9a4472806f90bd0fdde7772@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--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).