Bug 22262 - xfsdump stalls on file systems with real-time subvolume
Summary: xfsdump stalls on file systems with real-time subvolume
Status: RESOLVED OBSOLETE
Alias: None
Product: File System
Classification: Unclassified
Component: XFS (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: XFS Guru
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-07 05:24 UTC by ntrance1
Modified: 2013-12-10 22:36 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.32 and up
Tree: Mainline
Regression: No


Attachments

Description ntrance1 2010-11-07 05:24:53 UTC
The DirecTV DVR uses XFS file system with a real-time subvolume to store recordings.  In the process of trying to migrate recordings to larger drives, several users have found that xfsdump/xfsrestore no longer works in this situation.  The problem appears to occur with kernels 2.6.32 and later.  Here is an example of the process and output: 

mount -t xfs -o rtdev=/dev/sda3 /dev/sda2 /mnt/fap
mount -t xfs -o rtdev=/dev/sdb3 /dev/sdb2 /mnt/hr20
xfsdump -J - /mnt/hr20 | xfsrestore -J - /mnt/fap

<snip>
xfsdump: dumping directories
xfsrestore: examining media file 0
xfsrestore: dump description: 
xfsrestore: hostname: michael-desktop
xfsrestore: mount point: /mnt/hr20
xfsrestore: volume: /dev/sdd2
xfsrestore: session time: Wed Sep 15 22:38:21 2010
xfsrestore: level: 0
xfsrestore: session label: ""
xfsrestore: media label: ""
xfsrestore: file system id: def1a48a-e183-4371-b814-317bd7154611
xfsrestore: session id: ca19ec79-c4c9-41e1-9b8b-b70c4538131a
xfsrestore: media id: c130629b-ff0f-4acf-92a8-fa7174833814
xfsrestore: searching media for directory dump
xfsrestore: reading directories
xfsdump: dumping non-directory files
xfsrestore: 568 directories and 37729 entries processed
xfsrestore: directory post-processing
xfsrestore: restoring non-directory files
<stalls here>

I've tried versions of xfsdump from 2.2.48 through 3.0.4 and kernels 2.6.24 through 2.6.36, and have determined the problem occurs with kernels 2.6.32 and up.  Full test details here:
http://www.dbstalk.com/showthread.php?p=2585457#post2585457

Any help in fixing this issue would be appreciated.

Note You need to log in before you can comment on or make changes to this bug.