From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Linas Vepstas <linas@austin.ibm.com>,
reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
vitaly@thebsh.namesys.com, Jeff Mahoney <jeffm@suse.com>
Subject: Re: BUG in submit_ordered_buffer at fs/reiserfs/journal.c:616!
Date: Mon, 14 Mar 2005 14:50:53 -0500 [thread overview]
Message-ID: <200503141450.54309.mason@suse.com> (raw)
In-Reply-To: <42322C38.1040106@namesys.com>
On Friday 11 March 2005 18:39, Hans Reiser wrote:
> "I/O errors usually indicate bad hardware not bad software,
> probably you need to get a new disk and use dd_rescue to copy everything
This is your user friendly error message targeted at users that don't know
what an I/O error is?
What's an I/O error?
What's software?
What's hardware?
What's a disk?
What's dd_rescue?
How do I copy everything?
How do I put a new disk in?
How do I make the kernel recognize use new disk instead of the old one?
The list goes on and on. You'll never make the kernel more usable by making
messages in the syslog more verbose. You can make it more usable by having
consistent error messages that can be found via search engines or the manual.
Jeff's completely right here.
-chris
next prev parent reply other threads:[~2005-03-14 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 22:49 BUG in submit_ordered_buffer at fs/reiserfs/journal.c:616! Linas Vepstas
2005-03-11 23:39 ` Hans Reiser
2005-03-12 0:20 ` Jeff Mahoney
2005-03-14 19:50 ` Chris Mason [this message]
2005-04-13 19:11 ` Jeff Mahoney
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=200503141450.54309.mason@suse.com \
--to=mason@suse.com \
--cc=jeffm@suse.com \
--cc=linas@austin.ibm.com \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@thebsh.namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.