linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH] md - 0 of 7 - Introduction
Date: Fri, 23 Jan 2004 11:13:40 +1100	[thread overview]
Message-ID: <20040123105615.2237.patches@notabene> (raw)


Herewith, 7 more patches for drivers/md and related code.

The first fixes a lock-up that was introduced by a recent patch (as I
was worried might happen...).

The fourth makes device IO statistics work for md arrays.

The sixth, which depends on come code rearrangement in the 5th, is the
most significant of the patches. It allows md devices to be partitioned
(I finally figured out the *right* way to do this).

A second major number is dynamically allocated, and md arrays can be
created under this major as well as the traditional '9'.
Arrays created under the new major get 64 minor numbers, 63 of which
can be used for different partitions.

The arrays assembled under the new major are completely
separate from any arrays assembled under the old major (9).
(though an array created under one can be shut down and re-assembled
under another).

Currently this means that only 4 md arrays can be partitioned.
However once user-space catches up with the new 32bit device numbers
in the kernel, the limit will be many thousands.

Creating device nodes in /dev is left as a exercise for the reader
(as the major number can be different at each reboot).  Maybe devfs or
udev are solutions.

The allocated major number can be found by looking for "mdp" in
/proc/devices.

Partitioned md devices have names like
    md_dXpY
in /proc/partitions and /sys/block, are recommended to have names like
   /dev/md/dXpY
in /dev (X and Y are numbers).

Finally, the last (7th) patch is more of a sick joke than a serious
patch, though I would not object to it being included in the kernel.
Currently  devices that are not partitionable (e.g. md devices with
major '9') do not show up in /proc/partitions, which is a regression
from 2.4.   Maybe it is better to remove the "sgp->minors == 1" test,
but as Linus put that in.....

NeilBrown

             reply	other threads:[~2004-01-23  0:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  0:13 NeilBrown [this message]
2004-01-23  0:14 ` [PATCH] md - 1 of 7 - Fix possible hang in raid shutdown NeilBrown
2004-01-23  0:14 ` [PATCH] md - 2 of 7 - Move the test in preferred_minor to where it is used NeilBrown
2004-01-23  0:14 ` [PATCH] md - 3 of 7 - Fixes to make debuging output nicer NeilBrown
2004-01-23  0:14 ` [PATCH] md - 5 of 7 - Change the way the name of an md device is printed in error messages NeilBrown
2004-01-23  0:14 ` [PATCH] md - 4 of 7 - Collect device IO statistics for MD personalities NeilBrown
2004-01-23  0:14 ` [PATCH] md - 6 of 7 - Allow partitioning of MD devices NeilBrown
2004-01-23  0:14 ` [PATCH] md - 7 of 7 - Make sure md devices appear in /proc/partitions NeilBrown
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06  5:35 [PATCH] md - 0 of 7 - Introduction NeilBrown

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=20040123105615.2237.patches@notabene \
    --to=neilb@cse.unsw.edu.au \
    --cc=akpm@osdl.org \
    --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).