This code path wasn't touched until the change
in "mds/Server: fix stray reintegration". Now we
see that it will crash in fsstress in some circumstances
when the client is doing a link operation, where
we are checking the projected linkage on the DN
before going into this function, but not the projected
parenthood of the inode.
Signed-off-by: John Spray <john.spray@redhat.com>
Pull out the stray-handling code into a separate StrayManager
class.
There is an additional improvement to stray reintegration here,
by passing the DN that triggered the reintegration through,
we should make a better choice about *which* hardlink to
reintegrate the inode into, rather than just picking the first.
Fixes: #10390
Signed-off-by: John Spray <john.spray@redhat.com>
These are to be respected by the MDS in the number
of concurrent RADOS delete operations and
number of files to be purged at once.
Signed-off-by: John Spray <john.spray@redhat.com>
Previously this was simply hardcoded to do up to
10 RADOS delete ops at a time. Make this a config
option so that Filer consumers (like the MDS) can
know how many concurrent operations will be done
on their behalf.
Signed-off-by: John Spray <john.spray@redhat.com>
This happens because when handling an MCacheExpire,
we expire inodes first and then dentries, so when
the inodes are put() their dentries still are replicated
so eval_stray fails. Do an explicit call to maybe_eval_stray
when handling the expire for the dentry in order to catch
this.
One hits this path when migrating a stray away from
a stopping MDS rank.
Signed-off-by: John Spray <john.spray@redhat.com>
This was checking tracei's primary parent DN for remoteness
as a condition to calling eval_remote. However, the *primary*
parent DN in this case is the stray, which is not remote.
The correct check is tracedn (the remote dentry that got us here)
rather than tracei->get_parent_dn() (the primary dentry for the
inode that we have looked up).
This leads to eval_remote being invoked, and reintegration
of stray hard-linked inodes working.
Signed-off-by: John Spray <john.spray@redhat.com>
There was a bug in the arguments used by the splice function to move elements from the LRU list to the head of the list.
To simplify the implementation the direction of the LRU list has been changed e.g. newest entries are pushed in front.
Signed-off-by: Andreas-Joachim Peters <andreas.joachim.peters@cern.ch>
* asphyxiate needs more toolings, see
https://github.com/ceph/asphyxiate/issues/1
* this commit basically reverts c96064
* use `autodoxygen` directive to doxygen referenced source files
* do not call `doxygen` explicitly in `build-doc`, `autodoxygen`
will take care of it.
Fixes: #6115Fixes: #6115
Signed-off-by: Kefu Chai <kchai@redhat.com>
Retains old text format output when user specifies
a filename, else returns JSON. JSON output will
cope less well with large caches, but will be more
useful for automated tests.
Signed-off-by: John Spray <john.spray@redhat.com>
Fixes: #11159
Backport: hammer, firefly
Scripts required rgw_socket_path to exist in order to start radosgw.
This is not needed.
Reported-by: Dan Mick <dmick@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
(cherry picked from commit 6823bcdcd0)
During development each git commit cause currently a complete
rebuild of the source tree. By passing --disable-gitversion to
configure we set a generic version string for ceph to prevent
getting after each commit a new version set.
remove src/check_version and replace with a extended version
of src/make_version which allows detecting changes in .git_version
and ceph_ver.h to avoid not needed updates.
This change also forces to call make_version each time to make
sure that changes from configure or the NO_VERSION env variable
are processed.
Signed-off-by: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
Fixes: #11159
Backport: hammer, firefly
Scripts required rgw_socket_path to exist in order to start radosgw.
This is not needed.
Reported-by: Dan Mick <dmick@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
