From: Larkin Lowrey <llowrey@nuclearwinter.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] LVM commands extremely slow during raid check/resync
Date: Tue, 27 Mar 2012 16:24:15 -0500 [thread overview]
Message-ID: <4F722FFF.4010703@nuclearwinter.com> (raw)
In-Reply-To: <4F71CFFF.6090909@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]
I'll try the patches when I get a chance. In the mean time, I've
provided the info you requested as well as a "profiled" run of "lvcreate
-vvvv" attached as lvcreate.txt.gz. The file is pipe delimited with the
2nd field being the delta timestamps in ms between the current line and
the prior line. When that lvcreate was run all arrays, except md0, were
doing a check.
# pvs -a
PV VG Fmt Attr PSize PFree
/dev/Raid/Boot --- 0 0
/dev/Raid/Root --- 0 0
/dev/Raid/Swap --- 0 0
/dev/Raid/Videos --- 0 0
/dev/md0 Raid lvm2 a-- 496.00m 0
/dev/md1 Raid lvm2 a-- 2.03t 100.00g
/dev/md10 Raid lvm2 a-- 1.46t 0
/dev/md2 Raid lvm2 a-- 9.10t 0
# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md10 : active raid5 sdt1[6] sds1[5] sdm1[0] sdn1[1] sdl1[2] sdk1[4]
1562845120 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6]
[UUUUUU]
md2 : active raid5 sdr1[5] sdo1[4] sdq1[0] sdp1[3] sdg1[2] sdh1[1]
9767559680 blocks level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md0 : active raid6 sde1[4] sdc1[2] sdf1[5] sda1[1] sdb1[0] sdd1[3]
509952 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6]
[UUUUUU]
md1 : active raid5 sdb2[10] sde2[1] sdc2[3] sda2[9] sdd2[0] sdi2[6]
sdf2[4] sdj2[8]
2180641792 blocks super 1.2 level 5, 64k chunk, algorithm 2 [8/8]
[UUUUUUUU]
unused devices: <none>
--Larkin
On 3/27/2012 9:34 AM, Zdenek Kabelac wrote:
> Dne 27.3.2012 01:51, Larkin Lowrey napsal(a):
>> That helped bring the lvcreate time down from 2min to 1min so that's an
>> improvement. Thank you.
>>
>> The source of the remaining slowdown is the writing of metadata to my 4
>> PVs. The writes are small and the arrays are all raid5 so each metadata
>> write is also requiring a read. I'm still at a loss for why this was not
>> a problem when running F15 but the filter is a workable solution for me
>> so I'll leave it alone.
>>
>
> Could you please attach attach output of 'lvs -a' and eventually your md array
> setup.
>
> Ideally open regular bugzilla for f16.
>
> Zdenek
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
[-- Attachment #2: lvcreate.txt.gz --]
[-- Type: application/gzip, Size: 17163 bytes --]
next prev parent reply other threads:[~2012-03-27 21:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 7:56 [linux-lvm] LVM commands extremely slow during raid check/resync Larkin Lowrey
2012-03-26 13:02 ` James Candelaria
2012-03-26 17:49 ` Larkin Lowrey
2012-03-26 20:55 ` Ray Morris
2012-03-26 23:51 ` Larkin Lowrey
2012-03-27 14:34 ` Zdenek Kabelac
2012-03-27 21:24 ` Larkin Lowrey [this message]
2012-03-28 7:53 ` Zdenek Kabelac
2012-03-28 18:26 ` Stuart D Gathman
2012-03-29 0:27 ` Ray Morris
2012-03-29 9:48 ` Zdenek Kabelac
2012-03-27 14:31 ` Zdenek Kabelac
2012-03-27 18:11 ` Ray Morris
2012-03-27 20:36 ` Zdenek Kabelac
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=4F722FFF.4010703@nuclearwinter.com \
--to=llowrey@nuclearwinter.com \
--cc=linux-lvm@redhat.com \
--cc=zkabelac@redhat.com \
/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).