linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhilong Liu <zlliu@suse.com>
To: Jes.Sorensen@gmail.com
Cc: linux-raid@vger.kernel.org, Zhilong Liu <zlliu@suse.com>
Subject: [PATCH 2/3] mdadm/manpage: disable bitmap_resize for external file bitmap
Date: Tue,  5 Sep 2017 17:41:37 +0800	[thread overview]
Message-ID: <1504604498-26048-3-git-send-email-zlliu@suse.com> (raw)
In-Reply-To: <1504604498-26048-1-git-send-email-zlliu@suse.com>

Update the manpage in "SIZE CHANGES" against the md commit.
Commit: e8a27f836f165c26f867ece7f31eb5c811692319
(md/bitmap: disable bitmap_resize for file-backed bitmaps.)

Signed-off-by: Zhilong Liu <zlliu@suse.com>
---
 mdadm.8.in | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/mdadm.8.in b/mdadm.8.in
index e0747fb..f0fd1fc 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -2758,6 +2758,11 @@ Also the size of an array cannot be changed while it has an active
 bitmap.  If an array has a bitmap, it must be removed before the size
 can be changed. Once the change is complete a new bitmap can be created.
 
+.PP
+Note:
+.B "--grow --size"
+is not yet supported for external file bitmap.
+
 .SS RAID\-DEVICES CHANGES
 
 A RAID1 array can work with any number of devices from 1 upwards
-- 
2.6.6


  parent reply	other threads:[~2017-09-05  9:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05  9:41 [PATCH 0/3] mdadm patches for some trivial fixes Zhilong Liu
2017-09-05  9:41 ` [PATCH 1/3] mdadm/grow: Component size must be larger than chunk size Zhilong Liu
     [not found]   ` <20171005114430.GA24654@proton.igk.intel.com>
2017-10-07 12:17     ` Zhilong Liu
2017-10-07 12:31       ` Zhilong Liu
2017-10-09  3:32     ` Zhilong Liu
2017-10-09  7:17       ` Tomasz Majchrzak
2017-10-09 10:51       ` NeilBrown
2017-09-05  9:41 ` Zhilong Liu [this message]
2017-09-05  9:41 ` [PATCH 3/3] mdadm: fixes some trivial typos in comments Zhilong Liu
2017-10-02 20:00 ` [PATCH 0/3] mdadm patches for some trivial fixes Jes Sorensen

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=1504604498-26048-3-git-send-email-zlliu@suse.com \
    --to=zlliu@suse.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=linux-raid@vger.kernel.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 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).