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

Interop 2.6.0<->master lustre-rsync-test test_1: Error in replicating xattrs: fid2path error: Invalid argument

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • Lustre 2.7.0
    • server: 2.6.0
      client: lustre-master build # 2733
    • 3
    • 16497

    Description

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

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/0e01988c-68ff-11e4-9444-5254006e85c2.

      The sub-test test_1 failed with the following error:

      Error in replicating xattrs.
      
      == lustre-rsync-test test 1: Simple Replication == 07:14:40 (1415459680)
      CMD: onyx-44vm7 lctl --device lustre-MDT0000 changelog_register -n
      lustre-MDT0000: Registered changelog user cl1
      CMD: onyx-44vm7 lctl get_param -n mdd.lustre-MDT0000.changelog_users
      CMD: onyx-44vm7 dumpe2fs -h /dev/lvm-Role_MDS/P1 2>&1 |
      		grep -E -q '(ea_inode|large_xattr)'
      CMD: onyx-44vm7 dumpe2fs -h /dev/lvm-Role_MDS/P1 2>&1
      CMD: onyx-44vm7 dumpe2fs -h /dev/lvm-Role_MDS/P1 2>&1 |
      		grep -E -q '(ea_inode|large_xattr)'
      Replication #1
      ioctl err -22: Invalid argument (22)
      fid2path error: (/mnt/lustre, [0x200000400:0x12:0x0]) 22 Invalid argument
      Replication of operation failed(-22): 10 CREAT (1) [0x200000400:0x12:0x0] [0x200000400:0x11:0x0] 
      Replication of operation failed(-22): 17 HLINK (3) [0x200000400:0x14:0x0] [0x200000400:0xa:0x0] 
      Lustre filesystem: lustre
      MDT device: lustre-MDT0000
      Source: /mnt/lustre
      Target: /tmp/target
      Target: /tmp/target2
      Statuslog: /tmp/lustre_rsync.log
      Changelog registration: cl1
      Starting changelog record: 0
      Clear changelog after use: no
      Errors: 2
      lustre_rsync took 4 seconds
      Changelog records consumed: 18
      Replication #2
      Replication of operation failed(-17): 1 MKDIR (2) [0x200000400:0xa:0x0] [0x200000400:0x9:0x0] 
      Replication of operation failed(-17): 2 MKDIR (2) [0x200000400:0xb:0x0] [0x200000400:0x9:0x0] 
      Replication of operation failed(-17): 3 CREAT (1) [0x200000400:0xc:0x0] [0x200000400:0x9:0x0] 
      Replication of operation failed(-17): 4 CREAT (1) [0x200000400:0xd:0x0] [0x200000400:0xa:0x0] 
      Replication of operation failed(-17): 5 CREAT (1) [0x200000400:0xe:0x0] [0x200000400:0xa:0x0] 
      Replication of operation failed(-17): 6 CREAT (1) [0x200000400:0xf:0x0] [0x200000400:0xa:0x0] 
      Replication of operation failed(-17): 16 CREAT (1) [0x200000400:0x14:0x0] [0x200000400:0xa:0x0] 
      Replication of operation failed(-22): 17 HLINK (3) [0x200000400:0x14:0x0] [0x200000400:0xa:0x0] 
      Replication of operation failed(-17): 18 SLINK (4) [0x200000400:0x15:0x0] [0x200000400:0xa:0x0] 
      Error replicating  xattr for /tmp/target/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target2/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target2/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target2/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target2/d1.lustre-rsync-test/file5: 2
      Error replicating  xattr for /tmp/target2/d1.lustre-rsync-test/file5: 2
      Lustre filesystem: lustre
      MDT device: lustre-MDT0000
      Source: /mnt/lustre
      Target: /tmp/target
      Target: /tmp/target2
      Statuslog: /tmp/lustre_rsync.log
      Changelog registration: cl1
      Starting changelog record: 0
      Clear changelog after use: no
      Errors: 19
      lustre_rsync took 5 seconds
      Changelog records consumed: 22
      getfattr: /tmp/target/d1.lustre-rsync-test/file5: No such file or directory
      getfattr: /tmp/target2/d1.lustre-rsync-test/file5: No such file or directory
       lustre-rsync-test test_1: @@@@@@ FAIL: Error in replicating xattrs. 
      

      Info required for matching: lustre-rsync-test 1

      Attachments

        Issue Links

          Activity

            [LU-5907] Interop 2.6.0<->master lustre-rsync-test test_1: Error in replicating xattrs: fid2path error: Invalid argument
            adilger Andreas Dilger made changes -
            Fix Version/s Original: Lustre 2.7.0 [ 10631 ]
            Resolution New: Duplicate [ 3 ]
            Status Original: Reopened [ 4 ] New: Resolved [ 5 ]

            Closing as a duplicate of LU-5862, since nothing was landed under this ticket.

            adilger Andreas Dilger added a comment - Closing as a duplicate of LU-5862 , since nothing was landed under this ticket.
            adilger Andreas Dilger made changes -
            Resolution Original: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Reopened [ 4 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-5862 [ LU-5862 ]
            sarah Sarah Liu made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            hdoreau Henri Doreau (Inactive) added a comment - - edited

            Andreas, I think you're right and 0f22e4c098b1f7885ef509bbfc346b3e8905b28d introduced the issue. I must have missed something during my compatibility tests. The test succeeds when executed with the fix that is being reviewed for LU-5862 (see http://review.whamcloud.com/#/c/12574/).

            The ioctl error predates both patches (observed in Lustre 2.4 at least).

            hdoreau Henri Doreau (Inactive) added a comment - - edited Andreas, I think you're right and 0f22e4c098b1f7885ef509bbfc346b3e8905b28d introduced the issue. I must have missed something during my compatibility tests. The test succeeds when executed with the fix that is being reviewed for LU-5862 (see http://review.whamcloud.com/#/c/12574/ ). The ioctl error predates both patches (observed in Lustre 2.4 at least).
            hdoreau Henri Doreau (Inactive) made changes -
            Comment [ Andreas, I think you're right and 0f22e4c098b1f7885ef509bbfc346b3e8905b28d introduced the issue. I must have missed something during my compatibility tests.
            The fix that is being reviewed for LU-5864 might solve it though: http://review.whamcloud.com/#/c/12574/ ]

            There were several patches related to ChangeLog and fid2path that might have caused this, but they shouldn't have broken interoperability:

            commit 0f22e4c098b1f7885ef509bbfc346b3e8905b28d
            Author: Henri Doreau <henri.doreau@cea.fr>
            Date:   Fri Sep 19 15:39:56 2014 +0200
            
                LU-1996 lustre: Flexible changelog format.
                
                Added jobid fields to Changelog records (and extended records). The
                CLF_JOBID flags allows to check if the field is present or not (old
                format) when reading an entry. Jobids are expressed as 32 chars long,
                zero-terminated strings. Updated test_205 in sanity.sh.
                
                Signed-off-by: Henri Doreau <henri.doreau@cea.fr>
                Change-Id: Iacfe7099aa520e012535ac48c44793a1b86870a9
                Reviewed-on: http://review.whamcloud.com/4060
            
            commit b6e3612d845cf506e977f49aa85ddd1e709fd194
            Author: Henri Doreau <henri.doreau@cea.fr>
            Date:   Wed Oct 15 09:56:04 2014 +0200
            
                LU-3613 llite: Add ioctl to get parent fids from link EA.
                
                Added LL_IOC_GETPARENT to retrieve the <parent_fid>/name(s) of a given
                entry, based on its link EA. This saves multiple calls to
                path2fid/fid2path.
                
                Added llapi_path2parent() and llapi_fd2parent() wrappers.
                
                Added '--parents' option to lfs path2fid to call this function.
                
                New sanity test 154f to validate the behavior.
                
                Signed-off-by: Thomas Leibovici <thomas.leibovici@cea.fr>
                Signed-off-by: Henri Doreau <henri.doreau@cea.fr>
                Change-Id: I10f9316da605050be8fc709fe88d87abe86e22a4
                Reviewed-on: http://review.whamcloud.com/7069
            

            It is more likely the first one that is causing the problem. The patch should maintain compatibility, but I suspect it is not.

            adilger Andreas Dilger added a comment - There were several patches related to ChangeLog and fid2path that might have caused this, but they shouldn't have broken interoperability: commit 0f22e4c098b1f7885ef509bbfc346b3e8905b28d Author: Henri Doreau <henri.doreau@cea.fr> Date: Fri Sep 19 15:39:56 2014 +0200 LU-1996 lustre: Flexible changelog format. Added jobid fields to Changelog records (and extended records). The CLF_JOBID flags allows to check if the field is present or not (old format) when reading an entry. Jobids are expressed as 32 chars long, zero-terminated strings. Updated test_205 in sanity.sh. Signed-off-by: Henri Doreau <henri.doreau@cea.fr> Change-Id: Iacfe7099aa520e012535ac48c44793a1b86870a9 Reviewed-on: http://review.whamcloud.com/4060 commit b6e3612d845cf506e977f49aa85ddd1e709fd194 Author: Henri Doreau <henri.doreau@cea.fr> Date: Wed Oct 15 09:56:04 2014 +0200 LU-3613 llite: Add ioctl to get parent fids from link EA. Added LL_IOC_GETPARENT to retrieve the <parent_fid>/name(s) of a given entry, based on its link EA. This saves multiple calls to path2fid/fid2path. Added llapi_path2parent() and llapi_fd2parent() wrappers. Added '--parents' option to lfs path2fid to call this function. New sanity test 154f to validate the behavior. Signed-off-by: Thomas Leibovici <thomas.leibovici@cea.fr> Signed-off-by: Henri Doreau <henri.doreau@cea.fr> Change-Id: I10f9316da605050be8fc709fe88d87abe86e22a4 Reviewed-on: http://review.whamcloud.com/7069 It is more likely the first one that is causing the problem. The patch should maintain compatibility, but I suspect it is not.
            jlevi Jodi Levi (Inactive) made changes -
            Labels New: MB
            jlevi Jodi Levi (Inactive) made changes -
            Priority Original: Minor [ 4 ] New: Critical [ 2 ]

            People

              jamesanunez James Nunez (Inactive)
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: