From: Andreas Dilger <adilger@turbolabs.com>
To: Samuli Suonpaa <suonpaa@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.15pre7: kernel: invalidate: busy buffer
Date: Tue, 20 Nov 2001 12:53:41 -0700 [thread overview]
Message-ID: <20011120125341.Y1308@lynx.no> (raw)
In-Reply-To: <87itc5dysd.fsf@puck.erasmus.jurri.net>
In-Reply-To: <87itc5dysd.fsf@puck.erasmus.jurri.net>; from suonpaa@iki.fi on Tue, Nov 20, 2001 at 09:31:46PM +0200
On Nov 20, 2001 21:31 +0200, Samuli Suonpaa wrote:
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon last message repeated 55 times
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
>
> Since I do not know what this should tell me, I'd appreciate if
> somebody told me what this is all about. I can, of course, provide
> more information if necessary. But since I don't have a clue on what
> this would be related to (other that the printk seems to be in
> buffer.c) I have no idea of what information might be useful.
It means you are using LVM on a new kernel. Some day, the LVM code
will be changed so it doesn't do that. For now it is not a real
error, just a warning. It doesn't cause any real problems.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
prev parent reply other threads:[~2001-11-20 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 19:31 2.4.15pre7: kernel: invalidate: busy buffer Samuli Suonpaa
2001-11-20 19:52 ` Andrey Nekrasov
2001-11-20 19:53 ` Andreas Dilger [this message]
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=20011120125341.Y1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suonpaa@iki.fi \
/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.