lkml.org 
[lkml]   [2002]   [Nov]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: RFC - new raid superblock layout for md driver

    Steven> This is useful, atleast in the current raid implementation,
    Steven> because md_import can be changed to return an error if the
    Steven> device's unique identifier doesn't match the host identifier.
    Steven> In this way, each device of a RAID volume is individually
    Steven> locked to the specific host, and rejection occurs at import of
    Steven> the device time.

    This is a key issue on SANs as well. I think that having the hosts'
    UUID in the RAID superblock will allow rejection to happen
    gracefully. If needed, the user-land tools can have a --force
    option.

    Steven> Perhaps locking using the name field would work except that
    Steven> other userspace applications may reuse that name field for
    Steven> some other purpose, not providing any kind of uniqueness.

    I think the there needs to be two fields, a UUID field for the host
    owning the RAID superblocks, and then a name field so that the host,
    along with any other systems which can *view* the RAID superblock, can
    know the user defined name.

    John
    John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
    stoffel@lucent.com - http://www.lucent.com - 978-399-0479
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:31    [W:2.757 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site