[Dump-users] QFA for disk file wrong?

[Kenneth P. <sh...@se...>]

I'm dumping and generating a QFA file, and today tried to restore a large 
mbox file using it. The result was a gibberish 4k binary file that appeared 
to have selinux stuff in it. Using "restore -i" the file is shown to be 107 
Mbytes.

I'm now attempting the restore the hard way, without QFA, and expect it to 
take quite awhile as the dump is huge (140 Gbytes on a USB drive).

I'm pretty confident in the dump file, as I always do a -C verify and see 
the expected log files and more volatile user mailboxes miscompare.

I'm guessing that the QFA file is somehow wrong, but the short file size 
also worries me.

Dump command:

$DUMP 0u -h 0 -b 64 -f $DUMPSUBDIR/root/dump -Q $DUMPSUBDIR/root/qfa -B 
200000000 / -E ${EXCLUDE_FILE}

My attempted restore command:

restore -i -l -b 64 -f /mnt/Backup/0/root/dump -Q /mnt/Backup/0/root/qfa -vv

Version is dump-0.4b41-2.fc6.kp2.

Package changelog:

* Wed Mar 12 2008 Kenneth Porter <shi...@se...> 
0.4b41-2.fc6.kp2
- expectedinode patch to suppress error from unexpected inode on tape when 
comparing

* Tue Jan 08 2008 Kenneth Porter <shi...@se...> 
0.4b41-2.fc6.kp
- hugemodefile patch to handle very large file of mode settings

* Mon Aug 07 2006 Jindrich Novy <jn...@re...> 0.4b41-2.fc6
- fix miscompares detected by restore -C caused by SELinux (#189845)
- link properly against device-mapper and selinux libraries
- add autoconf BuildRequires
- use %{?dist}