mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jonathan bright" <jonathan.bright@onebox.com>
To: linux-kernel@vger.kernel.org
Subject: raid + xfs
Date: Fri, 29 Jun 2001 13:15:31 -0700	[thread overview]
Message-ID: <20010629201531.BNAU10107.mta05.onebox.com@onebox.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

hi.

i'm using xfs on top of raid, and have noticed some
unusual behavior.

my basic hardware configuration is 850 p3, intel d815eea2
motherboard, 4 ibm drives, 2 promise cards, and a separate
drive on built in ide channel as the root (this was not the
initial configuration, but kind of evolved as we went ahead.)

what we noticed was that the resyncing speed as reported by
cat /proc/mdstat was originally 100k/sec, making resyncing take
forever.  we bumped /proc/sys/dev/raid up, and got resyncing
to around 3000k/sec, with 90% cpu usage for raid5sync.

then i decided to run the bonnie benchmark, and *while*
bonnie was running, resyncing went up to 10000k, with low
CPU usage.  when bonnie finised, resyncing started to
behave badly again.  (and bonnie's performance wasn't noticably
impacted by the resyncing either).

perhaps in a few weeks i might be able to investigate the
raid code, but i'm hoping that someone might know what is
causing this behavior.

please CC me at jonathan.bright@onebox.com if you reply.

thanks,
jon bright

--
jonathan bright
jonathan.bright@onebox.com
415.820.7322 - voicemail/fax
www.brightconsulting.com

[-- Attachment #2: Type: application/octet-stream, Size: 2 bytes --]



[-- Attachment #3: Type: application/octet-stream, Size: 2 bytes --]



[-- Attachment #4: Type: application/octet-stream, Size: 2 bytes --]



             reply	other threads:[~2001-06-29 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29 20:15 jonathan bright [this message]
2003-12-10 13:31 RAID + XFS Zoltan NAGY

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=20010629201531.BNAU10107.mta05.onebox.com@onebox.com \
    --to=jonathan.bright@onebox.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

all inboxes | Powered by JetHome®