public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Emiliano Garcia <emi@vinyltribe.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.13 and above causes many "Invalidate: Busy Buffer" messages.
Date: 20 Nov 2001 10:51:38 -0800	[thread overview]
Message-ID: <1006282299.2189.0.camel@workstation> (raw)



My web server is running software raid 5 on two promise ultra66 cards
with an ALi alladin 5 chipset and a k6-2-500 with 300 megs of ram. The
setup is 2 20 gig Maxtor 5400 RPM drives and one WD 30 gig 7200 rpm
drive.. the raid size is 40 gigs, the chunks are 64kb, and I formated
with stride = 16. 

 I've noticed great improvements in the throughput of my raid with
hdparm -Tt /dev/md0 but now I get "Invalidate: Busy Buffer" hundreds of
times showing up in my dmesg. It only happens under heavy disk I/O and I
really need to figure out if this is just a warning or causing damage. A
dump causes this message to pop up at least 200 times. 

Please advise as to what I need to do to help troubleshoot or what the
fix is.

Emi.


                 reply	other threads:[~2001-11-20 18:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1006282299.2189.0.camel@workstation \
    --to=emi@vinyltribe.com \
    --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