Ceph » CephFS

I should mention that while client A was a user that has a path-restricted mds cap, the client B that "fixes" the EPERM is client.admin with unrestricted mds caps. I didn't try using his restricted cap to stat from a second machine.

I've confirmed that none of these help resolve these EPERM files:

• restart the ceph-fuse on client A
• mount with fuse_disable_pagecache = 1
• mount with fuse_default_permissions = 0

Ahh so it is related to path-restricted cap.
I tried as above with client B having the same client caps -- didn't fix the EPERM.

But when I remove the path-restricted cap, then remount, then the EPERM files can be stat'd.

Could it be that the fix for #17858 is incomplete?

Yup, in this case the diri is_stray (it looks like this

check_access stray_prior_path #10000ee3d6f/tmp_obj_x3Ncq5*

Relevant check is here, but I'm not sure how to turn #10000ee3d6f/tmp_obj_x3Ncq5 into the actual path.

int Session::check_access(CInode *in, unsigned mask,
                          int caller_uid, int caller_gid,
                          int new_uid, int new_gid)
{
  string path;
  CInode *diri = NULL;
  if (!in->is_base())
    diri = in->get_projected_parent_dn()->get_dir()->get_inode();
  if (diri && diri->is_stray()){
    path = in->get_projected_inode()->stray_prior_path;
    dout(20) << __func__ << " stray_prior_path " << path << dendl;
  } else {
    in->make_path_string(path, true);
    dout(20) << __func__ << " path " << path << dendl;
  }

path = in->get_projected_inode()->stray_prior_path; seems incorrect?

Thanks for this patch. It seems to fix the problem for our users.