All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Dmitri Monakhov <dmonakhov@openvz.org>
Cc: LKML <linux-fsdevel@vger.kernel.org>
Subject: Re: WARNING: at fs/buffer.c:1250 mark_buffer_dirty+0x7c/0x90()
Date: Tue, 10 Feb 2009 15:11:55 +0100	[thread overview]
Message-ID: <49918B2B.9040308@wpkg.org> (raw)
In-Reply-To: <m38woebf8k.fsf@dmon-lap.sw.ru>

Dmitri Monakhov schrieb:
> Tomasz Chmielewski <mangoo@wpkg.org> 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


  reply	other threads:[~2009-02-10 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 12:51 WARNING: at fs/buffer.c:1250 mark_buffer_dirty+0x7c/0x90() Tomasz Chmielewski
2009-02-10 13:20 ` Dmitri Monakhov
2009-02-10 14:11   ` Tomasz Chmielewski [this message]
2009-02-10 14:20 ` Jeff Mahoney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49918B2B.9040308@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=dmonakhov@openvz.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.