linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: PFC <lists@peufeu.com>
To: PFC <lists@peufeu.com>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: raid reconstruction speed
Date: Thu, 19 Jan 2006 22:29:37 +0100	[thread overview]
Message-ID: <op.s3m9znsqcigqcu@apollo13> (raw)
In-Reply-To: <op.s3m7n1pucigqcu@apollo13>


	Sorry for flooding ;)

	I have the following configuration :
	- two disks (hda and sda)
	- each disk has 2 partitions (hda1/sda1) and (hda2/sda2)
	- two raid1 md devices are made :
	md0 = sda1 + hda1, contains the OS
	md1 = sda2 + hda2, contains a database

	I made 2 devices because I wanted to use different FS's.

	When rebuilding md1, it does not realize accesses to md0 wait for the  
same disks. Thus reconstruction of md1 runs happily at full speed, and the  
machine is dog slow, because the OS and everything is on md0.
	(I cat /dev/zero to a file on md1 to slow the rebuild so it would let me  
start a web browser so I don't get bored to death)

	When rebuilding md0, the rebuild process detects accesses to md0 and  
behaves nicely (the machine is responsive). However, it does not realize  
that md1 is on the same disks, thus the databases are dog slow.

	Fortunately, as the rebuild runs ar full speed, the pain does not last  
long. It took 5 minutes to start this email client though.
	Thought you might wanna know ;)

	Regards,

	Pierre Caillaud

  reply	other threads:[~2006-01-19 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 12:02 Handling of read errors in raid6 Filipe Maia
2006-01-19 20:39 ` attempt to access beyond end of device PFC
2006-01-19 21:29   ` PFC [this message]
2006-01-19 22:10     ` raid reconstruction speed Mike Hardy
2006-01-19 23:27       ` Mark Hahn
2006-01-19 22:27     ` Neil Brown
2006-01-19 22:37       ` PFC

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=op.s3m9znsqcigqcu@apollo13 \
    --to=lists@peufeu.com \
    --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).