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

LFSCK doesn't detect missing LMV hash

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • Lustre 2.16.0
    • None
    • None
    • 3
    • 9223372036854775807

      I see a 2.15.3-based system in a similar to LU-16717 but not exactly the same state, an interrupted mdt->mdt migration left a directory in an inaccessible state:

      # lfs getdirstripe .
      lmv_stripe_count: 3 lmv_stripe_offset: 0 lmv_hash_type: none,migrating
      mdtidx FID[seq:oid:ver]
      0 [0x20002f9d0:0x6a:0x0]
      1 [0x240025042:0x62:0x0]
      1 [0x240025064:0x8e32:0x0]
      # touch test
      touch: cannot touch 'test': Bad file descriptor
      

      unlike the LU-16717 case, the directory has not "bad_type" flag and the flag did not appear after an LFSCK run. So I think the patches from LU-16717 would not help as the checks inside them need "bad_type" flag to be set.

            wc-triage WC Triage
            zam Alexander Zarochentsev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: