RHEL7/8/9: xfsrestore generated an orphanage directory unexpectedly

Solution Verified - Updated -

Issue

  • When restoring a backup created by xfsdump, xfsrestore created an orphanage directory
    and moved some files into it.

    $ xfsdump -L test -M test -f /scratch.dmp /mnt/test
...
xfsdump: NOTE: root ino 128 differs from mount dir ino 1024, bind mount?
...
xfsdump: Dump Status: SUCCESS

# xfsrestore -f /scratch.dmp /mnt/restore/
...
xfsrestore: restoring non-directory files
xfsrestore: NOTE: ino 128 salvaging file, placing in orphanage/1024.0/dir17/file60
xfsrestore: NOTE: ino 129 salvaging file, placing in orphanage/1024.0/dir17/file61
xfsrestore: NOTE: ino 130 salvaging file, placing in orphanage/1024.0/dir17/file62
xfsrestore: NOTE: ino 131 salvaging file, placing in orphanage/1024.0/dir17/file63
xfsrestore: NOTE: ino 132 salvaging file, placing in orphanage/1024.0/dir17/file64
xfsrestore: NOTE: ino 133 salvaging file, placing in orphanage/1024.0/dir17/file65
xfsrestore: NOTE: ino 134 salvaging file, placing in orphanage/1024.0/dir17/file66
...

Environment

  • Red Hat Enterprise Linux (RHEL) 7, 8 and 9
  • The issue happens with xfsdump generated by any of the following versions:
    • RHEL7: xfsdump-3.1.7-1.el7
    • RHEL8: xfsdump-3.1.8-2.el8
    • RHEL9: No released version of xfsdump generates dumps with the issue, but the issue can be hit when working on dumps from xfsdump on affected RHEL versions.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content