From: Pieter De Wit <pieter@insync.za.net>
To: stan@hardwarefreak.com, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Doesn't "writes" do what resync does ?
Date: Mon, 30 Dec 2013 21:36:02 +1300 [thread overview]
Message-ID: <52C13072.2060303@insync.za.net> (raw)
In-Reply-To: <52C11FDF.1040307@hardwarefreak.com>
On 30/12/2013 20:25, Stan Hoeppner wrote:
> On 12/29/2013 5:16 PM, Pieter De Wit wrote:
>> <snip>
>> Should that resync not have had more completed ?
> Your question is invalid. What you meant to ask is
>
> "Why are pvdisplay and mdstat reporting what seems to be conflicting
> state data?"
>
> Did you also ask on the lvm list why pvdisplay says most PEs are
> consumed, yet mdstat says resync is only 17% complete?
>
Hi again Stan,
pvdisplay says most PEs are consumed because I moved that data to the
device. My question, rephased then:
Shouldn't writes to a RAID device count as resyncs ?
Cheers,
Pieter
next prev parent reply other threads:[~2013-12-30 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 23:16 Doesn't "writes" do what resync does ? Pieter De Wit
2013-12-30 7:25 ` Stan Hoeppner
2013-12-30 8:36 ` Pieter De Wit [this message]
2013-12-30 11:39 ` Stan Hoeppner
2013-12-30 12:20 ` Pieter De Wit
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=52C13072.2060303@insync.za.net \
--to=pieter@insync.za.net \
--cc=linux-raid@vger.kernel.org \
--cc=stan@hardwarefreak.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 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.