public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jakob Østergaard" <jakob@unthought.net>
To: David Hajek <david@atrey.karlin.mff.cuni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: high cpu load with sw raid1
Date: Thu, 20 Sep 2001 12:38:23 +0200	[thread overview]
Message-ID: <20010920123823.B17911@unthought.net> (raw)
In-Reply-To: <20010920102616.A2753@pida.ulita.cz> <20010920111048.B17066@unthought.net> <20010920112342.A3253@pida.ulita.cz>
In-Reply-To: <20010920112342.A3253@pida.ulita.cz>; from david@atrey.karlin.mff.cuni.cz on Thu, Sep 20, 2001 at 11:23:42AM +0200

On Thu, Sep 20, 2001 at 11:23:42AM +0200, David Hajek wrote:
> Inlined.
> 
> On Thu, Sep 20, 2001, Jakob Rstergaard wrote:
> > On Thu, Sep 20, 2001 at 10:26:16AM +0200, David Hajek wrote:
> > > Hi,
> > > 
> > > I have linux box with 70GB SW Raid1. This box runs for half
> > > a year without problems but now I meet the high cpu load 
> > > problems. I suspect that it can be caused by not enough 
> > > free disk space on this md device. I see following:
> > > 
> > > 1 GB free  - load > 5
> > > 5 GB free  - load < 1
> > 
> > RAID does not know about "free space" (that is a filesystem thing), so that
> > would be either some strange interaction between the filesystem and lower
> > layers, or a measurement error - I guess.
> > 
> > High fragmentation could lead to extra filesystem activity, but that's not
> > really something the RAID can influence.
> 
> Why not? I do not say that it is cause be the RAID. It can be caused
> by filesystem. Do you think that fsck helps to defrag filesystem?

Ok, I was just trying to rule out the RAID.

I know for a fact that fsck does not defrag the filesystem.  However, if you
do run fsck, it will tell you how much is fragmented.

A few percent shouldn't matter.  But see what the fragmentation is when you
have only one gig available, compared to when you have five.

...
> 
> I use SCSI disks for this raid. Here is the output:
> 
> [root@marvin /root]# hdparm /dev/sda
> 
> /dev/sda:
>  readonly     =  0 (off)
>  geometry     = 8924/255/63, sectors = 143374738, start = 0
> [root@marvin /root]# hdparm -t /dev/sda
> 
>   /dev/sda:
>    Timing buffered disk reads:  64 MB in  1.87 seconds = 34.22 MB/sec
> [root@marvin /root]#   

Oh, silly me.  I'm mixing up mails here...  Sure, with SCSI you'll be fine.

> 
> I think disk speeds are ok - it works for really fine for half a year.

Yep.

If everything is slowed down by disk seeks due to high fragmentation, you
should actually be able to hear your disks seek like mad when the load is high.
Throughput doesn't matter much in that case - have you noticed the sound of
disk-heads (sonic booms, heads catching on fire, etc.)  ?

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2001-09-20 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20  8:26 high cpu load with sw raid1 David Hajek
2001-09-20  9:10 ` Jakob Østergaard
2001-09-20  9:23   ` David Hajek
2001-09-20 10:38     ` Jakob Østergaard [this message]
2001-09-20 18:40 ` Andreas Dilger
2001-09-21  7:07   ` David Hajek
2001-09-21  8:09     ` Andreas Dilger

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=20010920123823.B17911@unthought.net \
    --to=jakob@unthought.net \
    --cc=david@atrey.karlin.mff.cuni.cz \
    --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