1. 17 9月, 2010 2 次提交
    • S
      ceph: only send one flushsnap per cap_snap per mds session · e835124c
      Sage Weil 提交于
      Sending multiple flushsnap messages is problematic because we ignore
      the response if the tid doesn't match, and the server may only respond to
      each one once.  It's also a waste.
      
      So, skip cap_snaps that are already on the flushing list, unless the caller
      tells us to resend (because we are reconnecting).
      Signed-off-by: NSage Weil <sage@newdream.net>
      e835124c
    • S
      ceph: fix cap_snap and realm split · ae00d4f3
      Sage Weil 提交于
      The cap_snap creation/queueing relies on both the current i_head_snapc
      _and_ the i_snap_realm pointers being correct, so that the new cap_snap
      can properly reference the old context and the new i_head_snapc can be
      updated to reference the new snaprealm's context.  To fix this, we:
      
       - move inodes completely to the new (split) realm so that i_snap_realm
         is correct, and
       - generate the new snapc's _before_ queueing the cap_snaps in
         ceph_update_snap_trace().
      Signed-off-by: NSage Weil <sage@newdream.net>
      ae00d4f3
  2. 15 9月, 2010 2 次提交
  3. 14 9月, 2010 1 次提交
  4. 12 9月, 2010 4 次提交
  5. 29 8月, 2010 25 次提交
  6. 28 8月, 2010 6 次提交