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

setfacl default setting fail when nodemap enabled

    XMLWordPrintable

Details

    • Question/Request
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • Lustre 2.9
    • 9223372036854775807

    Description

      Hi ,

      When I setfacl default in lustre directory, I got unmapping group id(getfacl) after first setting(setfacl) . Then I execute setfacl command again and got fail ( Operation not permitted).

      1.cat /etc/passwd
      user1:x:1001:1001::/home/user1:/bin/bash

      2.nodemap setting
      nodemap.21b7e9f04fed448e.idmap=
      [
      .....

      { idtype: gid, client_id: 1001, fs_id: 23501 }

      ,
      .....
      ]

      3.setfacl steps
      [root@hsm client]# mkdir hadoop3
      [root@hsm client]# getfacl /mnt/client/hadoop3
      getfacl: Removing leading '/' from absolute path names

      1. file: mnt/client/hadoop3
      2. owner: root
      3. group: root
        user::rwx
        group::r-x
        other::r-x

      [root@hsm client]# setfacl -R -d -m group:user1:rwx /mnt/client/hadoop3
      [root@hsm client]# getfacl /mnt/client/hadoop3
      getfacl: Removing leading '/' from absolute path names

      1. file: mnt/client/hadoop3
      2. owner: root
      3. group: root
        user::rwx
        group::r-x
        other::r-x
        default:user::rwx
        default:group::r-x
        default:group:23501:rwx
        default:mask::rwx
        default:other::r-x

      [root@hsm client]# setfacl -R -d -m group:user1:rwx /mnt/client/hadoop3
      setfacl: /mnt/client/hadoop3: Operation not permitted

      Attachments

        Issue Links

          Activity

            People

              emoly.liu Emoly Liu
              sebg-crd-pm sebg-crd-pm (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: