From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Cc: Sebastian Riemer <sebastian.riemer@profitbricks.com>
Subject: mdadm 3.2.5: Assemble doesn't scale correctly
Date: Mon, 15 Oct 2012 18:13:12 +0200 [thread overview]
Message-ID: <507C3618.4030603@profitbricks.com> (raw)
Hi list,
the mdadm 3.2.5 assemble command doesn't scale correctly.
First, I've tested simple stuff with "strace" like this one:
# mdadm -A /dev/md0 /dev/loop0 /dev/loop1
This also scans imsm superblocks by reading files from "/sys/bus/pci".
Let's set it explicitly to 1.2:
# mdadm -A /dev/md0 -e 1.2 /dev/loop0 /dev/loop1
This results in approx. 100 lines less strace output.
But now the big performance killer:
Assemble()->open_dev_excl()->dev_open("%d:%d")->map_dev()
Why does this have to scan the whole "/dev" directory - not finding any
device with the same/wanted major:minor? Isn't there a better method?
It takes longer and longer the more devices are in /dev.
Cheers,
Sebastian
--
Sebastian Riemer
Linux Kernel Developer - Storage
next reply other threads:[~2012-10-15 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 16:13 Sebastian Riemer [this message]
2012-10-16 11:44 ` mdadm 3.2.5: Assemble doesn't scale correctly Sebastian Riemer
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=507C3618.4030603@profitbricks.com \
--to=sebastian.riemer@profitbricks.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).