>LVM manages to trigger the "raid5: switching cache buffer size" printk
>quiet voluminously when using a snapshot device. The following patch
>disables it by placing it under the debugging PRINTK macro.
Ben (and Ingo),
I happen to hit this message thousands of times per second sometimes under
normal operation in certain loads (raw devices for oracle and fs on LVM on
raid5). I understand that it's annoying, I actually think it shouldn't be
removed, because it's telling the operator importantn information.
As I understand it, the message is indicating a really bad performance
problem (i.e a complete flush of the stripe cache), and that anyone
encountering it on a very frequent (i.e. annoying) basis should consider
changing their setup.
Encountering this message has forced us to plan to split the single raid5
we have into two, in order to satisfy the different request sizes of the
raw-device vs. the ext3 fs.
David
P.S. Is there any hope of fixing this issue so that the stripe cache can
handle different sized requests? Possibly is this a bug in LVM?
-- /==============================\ | David Mansfield | | david@cobite.com | \==============================/- 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:32 EST