From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] silence an unnescessary raid5 debugging message
Date: Wed, 9 Oct 2002 04:55:27 -0700 [thread overview]
Message-ID: <20021009115527.GD10333@pegasys.ws> (raw)
In-Reply-To: <20021008210249.I15858@redhat.com>
On Tue, Oct 08, 2002 at 09:02:49PM -0400, Benjamin LaHaise wrote:
> On Tue, Oct 08, 2002 at 05:51:16PM -0700, David S. Miller wrote:
> > From: Benjamin LaHaise <bcrl@redhat.com>
> > Date: Tue, 8 Oct 2002 19:36:12 -0400
> >
> > As it stands, the syslogging from the printk does more damage to
> > performance than the underlying problem. Besides, LVM snapshots
> > are slow, but they're useful for a class of problems anyways.
> >
> > He's just saying kill the real problem first, that's all.
>
> I'm just saying that the message is the only real problem I have with
> the state of 2.4. Sure, 2.5 deserves it fixed correctly, but I doubt
> the correct fix will make it into 2.4 anytime soon (it's far more
> dangerous than we should consider shipping in a "stable" series).
It sound to me like a big nasty message should be generated
when the snapshot volume is created to advise that
performance will be horribly impaired. Thrashing the log
file to warn the user is like breaking your arm to remind
yourself to trim your fingernails.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2002-10-09 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 22:03 [patch] silence an unnescessary raid5 debugging message Benjamin LaHaise
2002-10-08 23:31 ` Neil Brown
2002-10-08 23:36 ` Benjamin LaHaise
2002-10-09 0:51 ` David S. Miller
2002-10-09 1:02 ` Benjamin LaHaise
2002-10-09 11:55 ` jw schultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 17:36 David Mansfield
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=20021009115527.GD10333@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
/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.