lkml.org 
[lkml]   [2009]   [Jun]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
    Neil Brown wrote:
    >
    > I am pleased to (finally) announce the availability of
    > mdadm version 3.0
    >
    > It is available at the usual places:
    > countrycode=xx.
    > http://www.${countrycode}kernel.org/pub/linux/utils/raid/mdadm/
    > and via git at
    > git://neil.brown.name/mdadm
    > http://neil.brown.name/git?p=mdadm
    >
    >
    > This is a major new version and as such should be treated with some
    > caution. However it has seen substantial testing and is considerred
    > to be ready for wide use.
    >
    >
    > The significant change which justifies the new major version number is
    > that mdadm can now handle metadata updates entirely in userspace.
    > This allows mdadm to support metadata formats that the kernel knows
    > nothing about.
    >
    > Currently two such metadata formats are supported:
    > - DDF - The SNIA standard format
    > - Intel Matrix - The metadata used by recent Intel ICH controlers.

    This seems pretty awful from a support standpoint: dmraid has been the
    sole provider of support for vendor-proprietary up until this point.

    Now Linux users -- and distro installers -- must choose between software
    RAID stack "MD" and software RAID stack "DM". That choice is made _not_
    based on features, but on knowing the underlying RAID metadata format
    that is required, and what features you need out of it.

    dmraid already supports
    - Intel RAID format, touched by Intel as recently as 2007
    - DDF, the SNIA standard format

    This obviously generates some relevant questions...

    1) Why? This obviously duplicates existing effort and code. The only
    compelling reason I see is RAID5 support, which DM lacks IIRC -- but the
    huge issue of user support and duplicated code remains.

    2) Adding container-like handling obviously moves MD in the direction of
    DM. Does that imply someone will be looking at integrating the two
    codebases, or will this begin to implement features also found in DM's
    codebase?

    3) What is the status of distro integration efforts? I wager the distro
    installer guys will grumble at having to choose among duplicated RAID
    code and formats.

    4) What is the plan for handling existing Intel RAID users (e.g. dmraid
    + Intel RAID)? Has Intel been contacted about dmraid issues? What does
    Intel think about this lovely user confusion shoved into their laps?

    5) Have the dmraid maintainer and DM folks been queried, given that you
    are duplicating their functionality via Intel and DDF RAID formats?
    What was their response, what issues were raised and resolved?

    Jeff





    \
     
     \ /
      Last update: 2009-06-02 22:15    [W:5.743 / U:0.000 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site