lkml.org 
[lkml]   [2007]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFD] Layering: Use-Case Composers (was: DRBD - what is it, anyways? [compare with e.g. NBD + MD raid])
    On Sun, 12 Aug 2007, Jan Engelhardt wrote:

    > On Aug 12 2007 13:35, Al Boldi wrote:
    >> Lars Ellenberg wrote:
    >>> meanwhile, please, anyone interessted,
    >>> the drbd paper for LinuxConf Eu 2007 is finalized.
    >>> http://www.drbd.org/fileadmin/drbd/publications/
    >>> drbd8.linux-conf.eu.2007.pdf
    >>>
    >>> but it does give a good overview about what DRBD actually is,
    >>> what exact problems it tries to solve,
    >>> and what developments to expect in the near future.
    >>>
    >>> so you can make up your mind about
    >>> "Do we need it?", and
    >>> "Why DRBD? Why not NBD + MD-RAID?"
    >
    > I may have made a mistake when asking for how it compares to NBD+MD.
    > Let me retry: what's the functional difference between
    > GFS2 on a DRBD .vs. GFS2 on a DAS SAN?

    GFS is a distributed filesystem, DRDB is a replicated block device. you
    wouldn't do GFS on top of DRDB, you would do ext2/3, XFS, etc

    DRDB is much closer to the NBD+MD option.

    now, I am not an expert on either option, but three are a couple things
    that I would question about the DRDB+MD option

    1. when the remote machine is down, how does MD deal with it for reads and
    writes?

    2. MD over local drive will alternate reads between mirrors (or so I've
    been told), doing so over the network is wrong.

    3. when writing, will MD wait for the network I/O to get the data saved on
    the backup before returning from the syscall? or can it sync the data out
    lazily

    >> Now, shared remote block access should theoretically be handled, as does
    >> DRBD, by a block layer driver, but realistically it may be more appropriate
    >> to let it be handled by the combining end user, like OCFS or GFS.

    there are times when you want to replicate at the block layer, and there
    are times when you want to have a filesystem do the work. don't force a
    filesystem on use-cases where a block device is the right answer.

    David Lang
    -
    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: 2007-08-12 18:47    [W:0.021 / U:0.936 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site