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

Failure on test suite sanity test_17k: get_xattr_names: llistxattr failed

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • None
    • Lustre 2.5.0
    • server and client: lustre-master build #1592
    • 3
    • 9563

    Description

      This issue was created by maloo for sarah <sarah@whamcloud.com>

      This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/06ab5688-fb67-11e2-8c6e-52540035b04c.

      The sub-test test_17k failed with the following error:

      rsync failed with xattrs enabled

      test log:

      == sanity test 17k: symlinks: rsync with xattrs enabled =========================== 15:23:56 (1375309436)
      sending incremental file list
      rsync: get_xattr_names: llistxattr(".",1024) failed: No data available (61)
      
      sent 18 bytes  received 12 bytes  60.00 bytes/sec
      total size is 0  speedup is 0.00
      rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]
       sanity test_17k: @@@@@@ FAIL: rsync failed with xattrs enabled 
      

      Attachments

        Issue Links

          Activity

            [LU-3713] Failure on test suite sanity test_17k: get_xattr_names: llistxattr failed
            pjones Peter Jones added a comment -

            This fix is being tracked under LU-3669

            pjones Peter Jones added a comment - This fix is being tracked under LU-3669

            This bug is currently causing failures on ZFS on the following:
            conf-sanity/61
            replay-single/58c
            sanityn/14[acd]
            sanityn/25a
            sanityn/72-73
            sanity/17k (obv)
            sanity/102[abcfhj]
            sanity/102ha
            sanity/103
            sanity/125
            sanity/154a
            sanity/162
            sanity/226a

            utopiabound Nathaniel Clark added a comment - This bug is currently causing failures on ZFS on the following: conf-sanity/61 replay-single/58c sanityn/14 [acd] sanityn/25a sanityn/72-73 sanity/17k (obv) sanity/102 [abcfhj] sanity/102ha sanity/103 sanity/125 sanity/154a sanity/162 sanity/226a
            pjones Peter Jones added a comment -

            Thanks Panda! Hongchao, could you please take care of this patch?

            pjones Peter Jones added a comment - Thanks Panda! Hongchao, could you please take care of this patch?
            panda Andrew Perepechko added a comment - Updated http://review.whamcloud.com/#/c/7208/

            I will update http://review.whamcloud.com/#/c/7208/ with a fix for listxattr/getxattr in MDT, since there would be some overlap between the patches anyway.

            panda Andrew Perepechko added a comment - I will update http://review.whamcloud.com/#/c/7208/ with a fix for listxattr/getxattr in MDT, since there would be some overlap between the patches anyway.
            panda Andrew Perepechko added a comment - - edited

            Hm, osd-zfs/osd_xattr.c:osd_xattr_list() changes lb->lb_buf ignoring that it's not its internal variable and may have a side-effect.

            int osd_xattr_list(const struct lu_env *env, struct dt_object *dt,
                            struct lu_buf *lb, struct lustre_capa *capa)
            {
            ...
                                    lb->lb_buf += rc;
            ...
                                    lb->lb_buf++;
            ...
            }
            

            The MDT code expects that lb_buf points to the beginning of the buffer with EA names, which is likely to be the same as the input, but may be different.

            panda Andrew Perepechko added a comment - - edited Hm, osd-zfs/osd_xattr.c:osd_xattr_list() changes lb->lb_buf ignoring that it's not its internal variable and may have a side-effect. int osd_xattr_list( const struct lu_env *env, struct dt_object *dt, struct lu_buf *lb, struct lustre_capa *capa) { ... lb->lb_buf += rc; ... lb->lb_buf++; ... } The MDT code expects that lb_buf points to the beginning of the buffer with EA names, which is likely to be the same as the input, but may be different.

            People

              hongchao.zhang Hongchao Zhang
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: