From: Wols Lists <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>,
Benjammin2068 <benjammin2068@gmail.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: WARNING: mismatch_cnt is not 0 on <array device>
Date: Tue, 8 Nov 2016 21:01:29 +0000 [thread overview]
Message-ID: <58223D29.6030401@youngman.org.uk> (raw)
In-Reply-To: <1497737a-a307-4501-4158-9703a051ef67@turmel.org>
On 08/11/16 20:38, Phil Turmel wrote:
> Have you added up the peak current draws of your drives to make sure
> your power supply keeps up when all drives are writing simultaneously
> (common with parity raid)?
On that point, be aware that many power supplies quote the sum of the
power to all rails. It could well be that the supply is nominally plenty
powerful enough, but the load on an individual rail is too high.
Cheers,
Wol
next prev parent reply other threads:[~2016-11-08 21:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 2:43 WARNING: mismatch_cnt is not 0 on <array device> Benjammin2068
2016-09-26 3:42 ` Brad Campbell
2016-09-26 7:19 ` Benjammin2068
2016-09-26 7:40 ` Brad Campbell
2016-09-26 19:47 ` Benjammin2068
2016-09-26 21:15 ` Phil Turmel
2016-09-27 1:08 ` Benjammin2068
2016-09-27 9:16 ` Brad Campbell
2016-09-27 16:27 ` Benjammin2068
2016-09-27 16:36 ` Roman Mamedov
2016-09-27 17:24 ` Benjammin2068
2016-09-27 16:45 ` Wols Lists
2016-09-27 17:30 ` Benjammin2068
2016-09-27 19:35 ` Wols Lists
2016-09-27 23:09 ` Adam Goryachev
2016-09-28 15:55 ` Benjammin2068
2016-10-02 17:33 ` Benjammin2068
[not found] ` <0f6bd6f6-20ee-1720-23fc-27d206063bfc@gmail.com>
2016-11-08 19:52 ` Benjammin2068
2016-11-08 19:53 ` Benjammin2068
2016-11-08 20:38 ` Phil Turmel
2016-11-08 21:01 ` Wols Lists [this message]
2016-11-09 19:00 ` Benjammin2068
2017-02-28 19:50 ` WARNING: mismatch_cnt is not 0 on <array device> [SOLVED?] Benjammin2068
2016-11-09 19:00 ` WARNING: mismatch_cnt is not 0 on <array device> Benjammin2068
2016-11-09 19:52 ` Benjammin2068
2016-09-27 6:42 ` Benjammin2068
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=58223D29.6030401@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=benjammin2068@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 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.