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

Recover OST specific directories after e2fsck

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • 3
    • 16839

    Description

      A backend storage issue caused an OST to get mounted read-only. Remounting showed that the journal entry in the superblock was corrupt. The journal was removed and e2fsck continued; fixing every issue moved all entries into lost+found directory (when mounting the OST as ldiskfs). Next the ext3 internal journal was added back using tune2fs -j /dev/sdd; and another e2fsck was run. It completed successfully. Using ll_recover_lost_found_objs, it appears that the object data is back in place, but there is no CONFIGS, quota_slave, or REMOTE_PARENT_DIR entries. Additionally the oi.* entries are missing as well as the health_check and last_rcvd files.

      Is there any way to recover these entries? In the e2fsck output we saw things that look like LU-2638 and also LU-2901.

      At this time e2fsck runs to completion and complains about block bitmap differences (lots of them), and Free blocks count (12519 of these messages).

      Attachments

        Activity

          People

            yujian Jian Yu
            hilljjornl Jason Hill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: