From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Johannes Stezenbach <js@sig21.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fat: excessive log spamming due to corrupted fs
References: <20100422155944.GA22181@sig21.net>
	<87633d2pm3.fsf@devron.myhome.or.jp>
	<20100427101423.GA30678@sig21.net>
	<87wrvt16p7.fsf@devron.myhome.or.jp>
	<874oiw26hd.fsf@devron.myhome.or.jp> <20100427173617.GA712@sig21.net>
Date: Wed, 28 Apr 2010 04:11:58 +0900
In-Reply-To: <20100427173617.GA712@sig21.net> (Johannes Stezenbach's message
	of "Tue, 27 Apr 2010 19:36:17 +0200")
Message-ID: <874oiwyakh.fsf@devron.myhome.or.jp>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.93 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1107
Lines: 27

Johannes Stezenbach <js@sig21.net> writes:

> On Wed, Apr 28, 2010 at 01:41:18AM +0900, OGAWA Hirofumi wrote:
>> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
>> 
>> >> comment about KERN_CONT in kernel.h.  But maybe it only happens
>> >> for /var/log/kern.log and my xconsole when generating too much
>> >> output too quickly, "dmesg -s 10000000 | less" did not show
>> >> the corruption (but only shows ~2700 lines out of the ~10000).
>> 
>> Um, please check syslog at same time with dmesg. If there is corruption
>> in syslog, but there is not in dmesg. It sounds like userland problem.
>
> I guess klogd cannot handle that much output.  If you'd add some
> rate limiting that might fix the log corruption, too.

I guess it meant the corruption is in only syslog. Ok, it explains this
problem.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
--
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/