1. 15 May, 2012 1 commit
  2. 02 May, 2012 2 commits
    • David Teigland's avatar
      gfs2: fix recovery during unmount · 1a058f52
      David Teigland authored
      Journal recovery from lock_dlm should not be ignored
      if there is an unmount in progress.  Ignoring it will
      causes the recovery to get stuck.  The recovery
      process will correctly handle an in-progess unmount.
      Signed-off-by: default avatarDavid Teigland <teigland@redhat.com>
      1a058f52
    • David Teigland's avatar
      dlm: fixes for nodir mode · 4875647a
      David Teigland authored
      The "nodir" mode (statically assign master nodes instead
      of using the resource directory) has always been highly
      experimental, and never seriously used.  This commit
      fixes a number of problems, making nodir much more usable.
      
      - Major change to recovery: recover all locks and restart
        all in-progress operations after recovery.  In some
        cases it's not possible to know which in-progess locks
        to recover, so recover all.  (Most require recovery
        in nodir mode anyway since rehashing changes most
        master nodes.)
      
      - Change the way nodir mode is enabled, from a command
        line mount arg passed through gfs2, into a sysfs
        file managed by dlm_controld, consistent with the
        other config settings.
      
      - Allow recovering MSTCPY locks on an rsb that has not
        yet been turned into a master copy.
      
      - Ignore RCOM_LOCK and RCOM_LOCK_REPLY recovery messages
        from a previous, aborted recovery cycle.  Base this
        on the local recovery status not being in the state
        where any nodes should be sending LOCK messages for the
        current recovery cycle.
      
      - Hold rsb lock around dlm_purge_mstcpy_locks() because it
        may run concurrently with dlm_recover_master_copy().
      
      - Maintain highbast on process-copy lkb's (in addition to
        the master as is usual), because the lkb can switch
        back and forth between being a master and being a
        process copy as the master node changes in recovery.
      
      - When recovering MSTCPY locks, flag rsb's that have
        non-empty convert or waiting queues for granting
        at the end of recovery.  (Rename flag from LOCKS_PURGED
        to RECOVER_GRANT and similar for the recovery function,
        because it's not only resources with purged locks
        that need grant a grant attempt.)
      
      - Replace a couple of unnecessary assertion panics with
        error messages.
      Signed-off-by: default avatarDavid Teigland <teigland@redhat.com>
      4875647a
  3. 26 Apr, 2012 5 commits
  4. 24 Apr, 2012 14 commits
  5. 23 Apr, 2012 18 commits