From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: WARNING: at fs/buffer.c:1250 mark_buffer_dirty+0x7c/0x90() Date: Tue, 10 Feb 2009 15:11:55 +0100 Message-ID: <49918B2B.9040308@wpkg.org> References: <4991786E.3080308@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: LKML To: Dmitri Monakhov Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:38861 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754435AbZBJOLx (ORCPT ); Tue, 10 Feb 2009 09:11:53 -0500 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Dmitri Monakhov schrieb: > Tomasz Chmielewski writes: > >> I've seen this warning on 2.6.29-rc3 when I removed a iSCSI device without >> unmounting a filesystem on it: > Block device has just burned under filesystem's feet (blkdev return > EIO for all requests.) What are you expect in this condition? Ask someone not familiar with kernel internals which message tells more: WARNING: at fs/buffer.c:1250 mark_buffer_dirty+0x7c/0x90() or: WARNING: Block device has just burned under filesystem's feet > As soon as i understand your systems is alive without any BUG or OOPS. > The only consequence is big-bada-boom message which is IMHO quite right. The "big-bada-boom message", "---[ cut here ]---" don't explain what happened, but rather "indicate a major problem" (as it's printed by kernel/panic.c). -- Tomasz Chmielewski http://wpkg.org