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

lfsck reports "XATTR trusted.fid: the parent FID is invalid"

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • Lustre 2.15.0
    • None
    • 3
    • 9223372036854775807

    Description

      LFSCK test reports "XATTR trusted.fid: the parent FID is invalid" error in the current 2.15 run.

      00100000:10000000:4.0:1637044175.473115:0:148585:0:(lfsck_namespace.c:264:lfsck_namespace_record_failure()) kjcf05-MDT0000-osd: namespace LFSCK hit first non-repaired inconsistency at the pos [2633473, [0x0:0x0:0x0], 0x0]
      00100000:10000000:26.0:1637044377.319767:0:148587:0:(lfsck_layout.c:4153:lfsck_layout_check_parent()) kjcf05-MDT0000-osd:([0x20000ea75:0xee9:0x0]|[0x0:0x0:0x0])/[0x100010000:0x6fb6352:0x0]:XATTR trusted.fid: the parent FID is invalid
      

      Will upload lfsck logs to the FTP.

       

      Attachments

        Issue Links

          Activity

            [LU-15333] lfsck reports "XATTR trusted.fid: the parent FID is invalid"

            Looks like a dup of https://jira.whamcloud.com/browse/LU-15683. Propose to close this one.

            scherementsev Sergey Cheremencev added a comment - Looks like a dup of https://jira.whamcloud.com/browse/LU-15683 . Propose to close this one.
            spitzcor Cory Spitz added a comment -

            Yes, Zam is investigating this issue. I believe it is fallout from LU-15404 where LFSCK is finding the non-Lustre EA inodes, which lack FID linkage. Since LFSCK does the right thing and reports the issue (while leaving it up to e2fsck to solve), I think we should resolve it as not a bug. Zam, do you agree? Please correct me if I'm wrong.

            spitzcor Cory Spitz added a comment - Yes, Zam is investigating this issue. I believe it is fallout from LU-15404 where LFSCK is finding the non-Lustre EA inodes, which lack FID linkage. Since LFSCK does the right thing and reports the issue (while leaving it up to e2fsck to solve), I think we should resolve it as not a bug. Zam, do you agree? Please correct me if I'm wrong.
            pjones Peter Jones added a comment -

            Cory

            Is someone from your team investigating this reported issue?

            Peter

            pjones Peter Jones added a comment - Cory Is someone from your team investigating this reported issue? Peter

            LFSCK logs uploaded to FTP.

            ftp> put lfsck_gc26b347.tar.gz
            local: lfsck_gc26b347.tar.gz remote: lfsck_gc26b347.tar.gz
            227 Entering Passive Mode (50,222,100,36,211,43).
            150 Ok to send data.
            226 Transfer complete.
            1875396 bytes sent in 0.0423 secs (44349.23 Kbytes/sec)
            ftp> pwd
            257 "/uploads/LU15333"
            ftp>
             
            prasannakumar Prasannakumar Nagasubramani added a comment - LFSCK logs uploaded to FTP. ftp> put lfsck_gc26b347.tar.gz local: lfsck_gc26b347.tar.gz remote: lfsck_gc26b347.tar.gz 227 Entering Passive Mode (50,222,100,36,211,43). 150 Ok to send data. 226 Transfer complete. 1875396 bytes sent in 0.0423 secs (44349.23 Kbytes/sec) ftp> pwd 257 "/uploads/LU15333" ftp>

            People

              zam Alexander Zarochentsev
              prasannakumar Prasannakumar Nagasubramani
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: