Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-12947

Project quotas: support of symlinks?

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • Lustre 2.12.3
    • None
    • CentOS 7.6, ldiskfs
    • 4
    • 9223372036854775807

    Description

      With Lustre 2.12.3 and project quotas enabled, we can't set a project ID on symlink. It would be useful to have symlink support to make project quotas more robust. Related to LU-11872 but that didn't fix the symlink support.

      #  lfs project -p 351945 -s -r eulig
      lfs: unable to get xattr for symlink 'eulig/projects/deepfluoro/wandb/run-20191106_123211-9o7biub9/train.py': Operation not supported
      

      Attachments

        Issue Links

          Activity

            [LU-12947] Project quotas: support of symlinks?

            This is being addressed under LU-11872.

            adilger Andreas Dilger added a comment - This is being addressed under LU-11872 .

            Oh that sounds good, thanks for the pointer! It's nice that it can be done in an atomic way.

            Also wanted to clarify that it's only a problem for already existing symlinks, as we confirmed that newly created symlinks in a directory (that has the inherit attribute set) are properly accounted for.

            sthiell Stephane Thiell added a comment - Oh that sounds good, thanks for the pointer! It's nice that it can be done in an atomic way. Also wanted to clarify that it's only a problem for already existing symlinks, as we confirmed that newly created symlinks in a directory (that has the inherit attribute set) are properly accounted for.

            There is a second patch https://review.whamcloud.com/34447 "LU-11872 utils: add option to recreate symlink files" that has not yet landed. As of today there is no way to "open" a symlink to change the projid. What the above patch proposes is to recreate the symlink with the correct projid, and then rename it on top of the old one.

            That should be atomic (i.e. no chance some user/app cannot find the symlink), and solves the issue of symlinks having the wrong projid.

            adilger Andreas Dilger added a comment - There is a second patch https://review.whamcloud.com/34447 " LU-11872 utils: add option to recreate symlink files " that has not yet landed. As of today there is no way to "open" a symlink to change the projid. What the above patch proposes is to recreate the symlink with the correct projid, and then rename it on top of the old one. That should be atomic (i.e. no chance some user/app cannot find the symlink), and solves the issue of symlinks having the wrong projid.

            People

              wshilong Wang Shilong (Inactive)
              sthiell Stephane Thiell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: