From: "Rainer Fügenstein" <rfu@oudeis.org>
To: Roman Mamedov <rm@romanrm.net>
Cc: Neil Brown <nfbrown@novell.com>, Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)
Date: Sun, 25 Oct 2015 20:23:37 +0100 [thread overview]
Message-ID: <16514313.20151025202337@oudeis.org> (raw)
In-Reply-To: <20151024213139.5b20dec6@natsu>
Hello Roman,
Saturday, October 24, 2015, 6:31:39 PM, you wrote:
> Use a higher bitmap-chunk size, such as 256M or more.
I guess that would be
mdadm --grow /dev/md0 --bitmap-chunk=256M ??
is it wise to issue this command during a re-sync?
a cron.weekly job started the re-sync (although I'm pretty sure this
job has been disabled quite some time ago)
$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdb1[7] sdf1[3] sdc1[5] sde1[0] sdd1[8]
11721061376 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
[==>..................] resync = 11.9% (348948608/2930265344) finish=7771.1min speed=5533K/sec
bitmap: 8/350 pages [32KB], 4096KB chunk
unused devices: <none>
tnx & cu
--
Best regards,
Rainer mailto:rfu@oudeis.org
next prev parent reply other threads:[~2015-10-25 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 13:38 kernel: BUG: soft lockup - CPU#1 stuck for 60s! [md0_raid5:1614] Rainer Fügenstein
2015-10-16 1:15 ` Neil Brown
2015-10-16 19:31 ` Rainer Fügenstein
2015-10-24 16:15 ` performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!) Rainer Fügenstein
2015-10-24 16:31 ` Roman Mamedov
2015-10-25 19:23 ` Rainer Fügenstein [this message]
2015-10-25 20:08 ` Neil Brown
2015-10-25 20:32 ` Rainer Fügenstein
2015-10-25 21:10 ` Neil Brown
2015-11-02 22:55 ` performance issue Rainer Fügenstein
2015-11-03 1:34 ` Neil Brown
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=16514313.20151025202337@oudeis.org \
--to=rfu@oudeis.org \
--cc=linux-raid@vger.kernel.org \
--cc=nfbrown@novell.com \
--cc=rm@romanrm.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.