linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.0test9 Reiserfs boot time "buffer layer error at fs/buffer.c:431"
Date: Wed, 29 Oct 2003 23:49:54 +0200	[thread overview]
Message-ID: <200310292149.h9TLnsNq024151@car.linuxhacker.ru> (raw)
In-Reply-To: 20031029123107.338796a4.akpm@osdl.org

Hello!

Andrew Morton <akpm@osdl.org> wrote:
>> Here are the results (output of dmesg) from booting a kernel with this
>> patch:
>> set_blocksize: size=4096
>> buffer layer error at fs/buffer.c:431
AM> hm, that didn't tell us much :(
AM> Could you add Oleg's patch as well?

Actually it will say that device's block size is 4096 (confirming
last set_blocksize was at least partially succesful), but what
it does not tell us is how those buffers have survived after blocksize
was changed and all buffers were invalidated.
(These buffers are there because reiserfs first reads that offset (in bytes)
with whatever current blocksize is, except they should have been invalidated of
course).
Even if invalidate_bdev() -> invalidate_inode_pages() have not cleaned
everything, truncate_inode_pages() should have done this.
So probably this page means do_invalidate_page() ... -> try_to_free_buffers()
have failed for whatever reason.
We did not write there yet, so this is not PageWriteback case.
But if the read is still going on, I guess we won't free the page/buffers?
Or am I missing some wait_on_buffer()?
But anyway that might explains buffers being still in page, but not such
a page present in a mapping. (except if we have not pickup this page from a list
of free pages not looking that it still have stale buffers)

Bye,
    Oleg

  reply	other threads:[~2003-10-29 21:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 15:49 2.6.0test9 Reiserfs boot time "buffer layer error at fs/buffer.c:431" lkml-031028
2003-10-28 18:36 ` Hans Reiser
2003-10-28 20:27 ` Oleg Drokin
2003-10-28 22:13 ` Andrew Morton
2003-10-28 22:15   ` Hans Reiser
2003-10-29  6:56   ` lkml-031028
2003-10-29 17:44   ` lkml-031028
2003-10-29 20:31     ` Andrew Morton
2003-10-29 21:49       ` Oleg Drokin [this message]
2003-10-29 22:19         ` Andrew Morton
2003-10-30  6:22           ` lkml-031028
2003-10-30  6:51           ` lkml-031028
2003-11-02  7:17           ` Herbert Xu
2003-11-02  7:33             ` Andrew Morton
2003-11-02  9:18               ` Oleg Drokin
2003-11-02  9:27               ` Herbert Xu
2003-11-02  9:40                 ` Andrew Morton
2003-11-02  9:54                   ` Herbert Xu
2003-11-02 11:54                     ` Hans Reiser
2003-11-02 21:09                       ` Herbert Xu
2003-11-03 10:20                         ` Stephan von Krawczynski
2003-11-04  8:10                           ` Hans Reiser
2003-11-04 21:03                             ` Debian Kernels was: " Mike Fedyk
2003-11-04  9:54                               ` Hans Reiser
2003-11-04 23:49                               ` Stephan von Krawczynski
2003-11-05  0:05                                 ` Mike Fedyk
2003-11-16 13:05                                 ` Pavel Machek
2003-11-16  3:55                                   ` Hans Reiser
2003-11-16 14:15                                   ` Stephan von Krawczynski
2003-11-16 17:05                                     ` Pavel Machek
2003-11-16 17:27                                       ` Valdis.Kletnieks
2003-11-16 17:40                                         ` Stephan von Krawczynski
2003-11-16 18:38                                           ` Valdis.Kletnieks
2003-11-16 22:54                                             ` Stephan von Krawczynski
2003-11-16 17:30                                       ` Stephan von Krawczynski
2003-11-02 11:50                 ` Hans Reiser
2003-11-02 20:33                   ` Herbert Xu

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=200310292149.h9TLnsNq024151@car.linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).