mds: log before respawning when standby-replay falls behind

Call into an MDS method so that we can write to the log.

Signed-off-by: Sage Weil <sage@inktank.com>
rgw: Fix return value for swift user not found

http://tracker.ceph.com/issues/1779 fixes #1779

Adjust the return value from rgw_get_user_info_by_swift call
in RGW_SWIFT_Auth_Get::execute() to have the correct
return code in response.
Merge pull request #385 from kri5/wip-1779

rgw: Fix return value for swift user not found

Reviewed-by: Yehuda Sadeh <yehuda@inktank.com>
librados: fix test warning on 32-bit platforms

Signed-off-by: Sage Weil <sage@inktank.com>
mon: Paxos: update first_committed on first paxos proposal

We were adding this update to a transaction that would only be applied
on the leader.  The peons would never see a first_committed > 0.

Fixes: #5484

Signed-off-by: Joao Eduardo Luis <joao.luis@inktank.com>
Reviewed-by: Sage Weil <sage@inktank.com>
doc: Minor fix.

Signed-off-by: John Wilkins <john.wilkins@inktank.com>
set object_info_t pool of an ObjectContext if it is undefined or bad

When reading object_info_t from an existing object attribute, the pool
may be < 0 and should be set to the pool containing the object. This is done
on the oi object on the stack but overriden later by:

    obc->obs.oi.decode(bv);

The oi object on the stack is removed and the pool of obc->obs.oi.oloc
is fixed, if necessary. The object_info_t is only decoded once instead
of twice. The ObjectContext constructor only copies the object_info_t
to a data member and does not make use of it. The object_info_t
constructor used by the oi variable on the stack is exactly equivalent
to creating the object with the default constructor and calling the
decode() immediately afterwards.

Signed-off-by: Loic Dachary <loic@dachary.org>