From: Andrew Morton <akpm@zip.com.au>
To: Ryan Mack <rmack@mackman.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] dmesg: "invalidate: busy buffer"
Date: Wed, 30 Jan 2002 17:54:59 -0800 [thread overview]
Message-ID: <3C58A3F3.7F1002D9@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0201301717340.9601-100000@mackman.net>
Ryan Mack wrote:
>
> The last two days my dmesg buffer has be filled with "invalidate: busy
> buffer" messages. I tried rebooting (and forcing a fsck), but after about
> 12 hours they came back.
>
> I'm running 2.4.17 on a dual P3, Intel 440BX chipset. Both filesystems
> are raid mirrored, ext3, ordered-data mode. One mirrored pair is on a
> Adaptec AHA-2940U2/W controller (actually, this is running in degraded
> mode, damn defective IBM UltraStar failed on me). The other mirrored pair
> is on two Intel PIIX4 IDE controllers.
>
> Since one of the raid pairs is down to a single drive, I've been backing
> it up to the other mirrored pair nightly using dump 0.4b22 and, more
> recently, dump 0.4b26.
This is due to some userspace application calling
ioctl(BLKFLSBUF); The kernel calls invalidate_buffers()
against a live device so it can of course sometimes
encounter a locked buffer, and it spits this message.
> Any thoughts what's causing this? Am I at risk for data loss?
No, there's no risk. I think the invalidate_buffers()
call should only be made within the ioctl if the device's
usage count is one, but various kernel luminaries didn't
like the idea, for reasons which I failed to understand :)
-
prev parent reply other threads:[~2002-01-31 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 1:24 [BUG] dmesg: "invalidate: busy buffer" Ryan Mack
2002-01-31 1:54 ` Andrew Morton [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=3C58A3F3.7F1002D9@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rmack@mackman.net \
/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