linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Heinzmann <Robert.Heinzmann@gmx.net>
To: linux-raid@vger.kernel.org
Subject: mdadm 2.2 new option
Date: Thu, 15 Dec 2005 23:14:02 +0100	[thread overview]
Message-ID: <43A1EAAA.6090802@gmx.net> (raw)

Hello,

i just downloaded the mdadm 2.2 version. It seems that there are some 
new options which are not explained in details. of special interest are 
2 options.

-GROW
The new grow mode is very very helpfull for us. It would allow us to do 
resize operations with md devices at last - without the need for LVM.
The manpage states that the GROW mode requires kernel support to work. 
There is no note that states, which kernel supports the options. Also 
with various distributions with patched kernels its not possible to say 
version X.Y.Z. of the kernel contains the required patches.

Is there a way to find out via mdadm, if the current kernel supports the 
GROW mode, prior to performing the GROW ?

-bitmap

As far as I understand this bitmap options, in incorperates write intend 
logging.
Is this based on paper by James Bottomley ? Also is there a way to find 
out via mdadm if the running kernel supports intend logging via mdadm ?

-There is also an option --write-mostly since 2.0.

I guess this especially usefull for MD devices with large storage arrays 
as backend. They have clever caches and read ahead paramaters, that can 
be non-effective if we change the disk for each read. Does this option 
require a kernel modification too ?

One last question. Besindes the source code and manpage is there oterh 
documentation available on how the md works internally ? (update of 
superblock, handling of device renaming inside the superblock etc.)

Thanks,
Robert Heinzmann

             reply	other threads:[~2005-12-15 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 22:14 Robert Heinzmann [this message]
2005-12-16  1:50 ` mdadm 2.2 new option 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=43A1EAAA.6090802@gmx.net \
    --to=robert.heinzmann@gmx.net \
    --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).