From: berk walker <berk.walker@verizon.net>
To: "Jason C. Leach" <jleach@ocis.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: I/O Blocking
Date: Thu, 22 Jul 2004 21:47:28 -0400 [thread overview]
Message-ID: <41006E30.7050204@verizon.net> (raw)
In-Reply-To: <40FFEB55.2000905@ocis.net>
Jason C. Leach wrote:
> Hi,
>
> Both the RAID (Promise SuperTrak 6000) or the USB subsystems really
> drive the system load up. I'm using a AMD 3200+ system that is only a
> few months old with the 2.4.25 kernel. When the I/O systems are
> blocking the system is very unresponsive. Some times samba will
> timeout, or I'll wait several seconds for commands like df, top, w and
> so on.
>
> I am wondering if I were to use a dual CPU system, would this solve my
> I/O blocking problem? Would one CPU tend to the I/O subsystem and the
> second would deal with other system requests I (samba, DB, LDAP, ...)?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
HMMM I seemed to have lost the 1st of the thread, 2 cents worth .. what
ya pay for ...
I might be supect of the m/b IDE channels (personally had lots of
failures) - SMART drives that are not configured as SMART (sorry, I
always use Intel, AMD...?) enableing in bios and kernel or mod might
give clues. I, also, think that there must be an IRQ conflict, IRQ
unanswered, or same ilk.
You could test by swapping drives, swapping m/b's. What sizes are your
disks? What RAM do you use,, I do have a plethora of hwde I could loan.
b-
prev parent reply other threads:[~2004-07-23 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 16:29 I/O Blocking Jason C. Leach
2004-07-22 18:02 ` Guy
2004-07-22 18:09 ` Jason C. Leach
2004-07-22 18:37 ` Guy
2004-07-22 19:51 ` Kanoa Withington
2004-07-23 1:47 ` berk walker [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=41006E30.7050204@verizon.net \
--to=berk.walker@verizon.net \
--cc=jleach@ocis.net \
--cc=linux-raid@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).