linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>
Subject: Re: [linux-lvm] lvextend doesn't sync raid1 LV
Date: Mon, 28 Jan 2019 11:07:28 +0100	[thread overview]
Message-ID: <4372d8da-e5d8-fba9-dba8-aee7d8e763b4@redhat.com> (raw)
In-Reply-To: <0572fd11-c137-3def-cf63-3c796de07cf2@strike.wu.ac.at>

Dne 25. 01. 19 v 18:33 Alexander 'Leo' Bergolth napsal(a):
> Hi!
> 
> If I extend a raid1 LV using lvextend, the newly allocated space in the two rimage devices isn't synced, just like if I had used the option --nosync.
> 
> As a result, a following raid check will report mismatches.
> 

Hi

Please open  BZ  for lvm2 https://bugzilla.redhat.com/enter_bug.cgi
and submit all your findings there.

Regards

Zdenek

      reply	other threads:[~2019-01-28 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 17:33 [linux-lvm] lvextend doesn't sync raid1 LV Alexander 'Leo' Bergolth
2019-01-28 10:07 ` Zdenek Kabelac [this message]

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=4372d8da-e5d8-fba9-dba8-aee7d8e763b4@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=leo@strike.wu.ac.at \
    --cc=linux-lvm@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).