On Dec 3, 2006, at 12:06 PM, Kern Sibbald wrote:
On Sunday 03 December 2006 20:57, Landon Fuller wrote:On Dec 3, 2006, at 11:41 AM, Kern Sibbald wrote:On Sunday 03 December 2006 19:46, Landon Fuller wrote:Signature validation is done on what is actually written to disk (upon restore). Thus sparse blocks will be read() as zeros, and the signature would be correct.No, sorry, but you have it backwards. You were passing blocks of zeros to the digest subroutines during the backup process. Those blocks are *not* written to the Volume, and thus they are not written to the disk during the restore. If they were written to the disk during restore some sparse files that haveonly one or two blocks could suddenly become monsterous.
I think we might be talking past each other. =)At the end of file restore, when the signature is computed, it's computed by read()'ing the file in from disk. The sparse blocks are still read() as zero-filled blocks of zeros, even if they are file-system sparse, and then passed to the digest routines. The purpose of reading from disk was to ensure that what got written to disk exactly matched what was originally read from disk.
PGP.sig
Description: This is a digitally signed message part
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
