A recent mod changed the number of phases in xfsdump, and consequently the

xfsdump output changed. This mod fixes the expected output for the xfsdump
tests, as well as a few other minor bugs I came across when running the
xfsdump qa tests.
This commit is contained in:
Bill Kendall
2006-06-08 12:50:04 +00:00
parent 543e4a76fa
commit 64e89fe895
30 changed files with 179 additions and 294 deletions
+3 -7
View File
@@ -9,16 +9,13 @@ xfsdump: level 0 dump of HOSTNAME:SCRATCH_MNT
xfsdump: dump date: DATE
xfsdump: session id: ID
xfsdump: session label: "stress_039"
xfsdump: ino map phase 1: skipping (no subtrees specified)
xfsdump: ino map phase 2: constructing initial dump list
xfsdump: ino map phase 3: skipping (no pruning necessary)
xfsdump: ino map phase 4: skipping (size estimated in phase 2)
xfsdump: ino map phase 5: skipping (only one dump stream)
xfsdump: ino map phase 1: constructing initial dump list
xfsdump: ino map phase 2: skipping (no pruning necessary)
xfsdump: ino map phase 3: skipping (only one dump stream)
xfsdump: ino map construction complete
xfsdump: estimated dump size: NUM bytes
xfsdump: /var/xfsdump/inventory created
xfsdump: preparing drive
xfsdump: WARNING: using default tape file size: 256 Mb (use -d option to adjust file size)
xfsdump: media block size: 0 bytes
xfsdump: WARNING: media may contain data. Overwrite option specified
xfsdump: creating dump session media file 0 (media 0, file 0)
@@ -47,7 +44,6 @@ xfsrestore: using scsi tape (drive_scsitape) strategy
xfsrestore: using online session inventory
xfsrestore: searching media for directory dump
xfsrestore: preparing drive
xfsrestore: WARNING: using default tape file size: 256 Mb (use -d option to adjust file size)
xfsrestore: examining media file 0
xfsrestore: reading directories
xfsrestore: 3 directories and 38 entries processed