rpm: unconditionally package rbd-replay-prep(8)

The build system will conditionally build and install the
rbd-replay-prep utility based on the presence of lttng.

Commit 230c5b8e7f58e2e8be32c3f31c6abcc5bdabc5ca adjusted the RPM
packaging so that we only package and ship the rbd-replay-prep utility
and its man page when we're on a platform that has lttng.

The problem is that this is only half-correct. The build system
unconditionally installs the man page for rbd-replay-prep, regardless of
whether lttng was present or absent, and (by extension,) without regard
for whether we've built and installed the rbd-replay-prep binary or not.

We have two options: either the build system should be adjusted to
conditionally skip installing rbd-replay-prep(8), or else we should just
adjust the RPM packaging to always ship the man page. This commit does
the latter.

Backport: firefly
Signed-off-by: Ken Dreyer <kdreyer@redhat.com>
osd: log message content cosmetics

Signed-off-by: Loic Dachary <ldachary@redhat.com>
Merge pull request #3032 from dachary/wip-osd-log-cosmetics

osd: log message content cosmetics

Reviewed-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@redhat.com>
doc: minor fix in ceph-authtool man page

Signed-off-by: Abhishek Lekshmanan <abhishek.lekshmanan@gmail.com>
Merge pull request #3023 from ktdreyer/rpm-rbd-replay-prep-conditional

rpm: unconditionally package rbd-replay-prep(8)

Reviewed-by: Adam Crume <adamcrume@gmail.com>
Merge pull request #3019 from theanalyst/doc/typo/ceph-auth

doc: minor fix in ceph-authtool man page

Reviewed-by: Loic Dachary <ldachary@redhat.com>
added consts, cleanup
Signed-off-by: Michal Jarzabek <stiopa@gmail.com>
Merge pull request #3037 from stiopaa1/cleanup

added some consts, some cleanup

Reviewed-by: Loic Dachary <ldachary@redhat.com>
mds: fix MDLog I/O callback without finisher

This could deadlock if another caller was waiting
on a write_head callback while holding mds_lock.

Signed-off-by: John Spray <john.spray@redhat.com>
mds: in segment expiry, use end instead of start

Previously we were always leaving the last log
segment un-expired from Journaler's POV, because
we were updating expire_pos to the *start* of the
expired journal segment instead of the *end*.

This was harmless, but cleaning it up makes it
easier to see what's going on during journal flushes
in testing.

Signed-off-by: John Spray <john.spray@redhat.com>
mds: implement "flush journal" asok

Start a new segment and flush everything older
to the backing store.

Signed-off-by: John Spray <john.spray@redhat.com>