[lkml]   [2002]   [Oct]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] silence an unnescessary raid5 debugging message
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 <>
> > 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:

Remember Cernan and Schmitt
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:29    [W:0.039 / U:4.076 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site