Re: [patch] silence an unnescessary raid5 debugging message

From: jw schultz (jw@pegasys.ws)
Date: Wed Oct 09 2002 - 06:55:27 EST


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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:30 EST