kubernetes/examples

cephfs subvolume uid, gid information not retain after mounting the subvolumegroup

zeddit opened this issue · 5 comments

zeddit commented

I created a subvolumegroup with default settings as:

ceph fs subvolume create myfs mysvg

then I add some subvolumes under the subvolumegroup with uid,gid settings, like:

ceph fs subvolume create myfs user1 --size 10737418240 --group_name mysvg --uid 190002 --gid 19001 --mode 640 --namespace-isolated

then I try to mount the subvolumegroup from host os and k8s pod like:

sudo mount -t ceph -o mds_namespace=myfs,name=user1,secret=AQA9CxBkqx+CAhABF2Gu+f7vybws6HkAO2KKYg== 10.0.26.1:6789:/volumes/mysvg /mnt

and

   - name: cephfs
        cephfs:
          monitors:
            - 10.0.26.1:6789
            - 10.0.26.2:6789
            - 10.0.26.3:6789
          user: user1
          secretRef:
            name: rook-ceph-client-aitopia
          path: "/volumes/mysvg"

However, all subvolumes have user and group as root and root, where I expect should be the uid and gid I have set.
Is there any configuration that I missed, I can find few documentations about this topic.

Great thanks.

zeddit commented

I have checked the uid and gid of subvolumes with ceph fs subvolume info and the results show that the uid and gid was set correctly. However, after mount, these identity information lost.

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.