fbackup block read size less than block written

[Ron Markarian]

Here is the final output of my fbackup log. The errors were just files in use. I don't understand why the blocks written is larger than the blocks read. Please educate me.

fbackup(1005): run time: 2784 seconds
fbackup(1030): warnings encountered during backup
fbackup(3055): total file blocks read for backup: 3993181
fbackup(3056): total blocks written to output file /dev/rmt/c2t6d0BEST: 4173746

[Steven E. Protter]

I think it writes an extra tape block for the directory of whats on the tape.

SEP

[A. Clay Stephenson]

Sparse files could very easily account for this.

[Todd McDaniel_1 · Accepted solution]

could be the block size is different for the fbackup than it is on your system... so it would require more blocks if they are smaller for the fbackup.

Larger block size will allow more data in a block, smaller block size on backup will require more blocks.

I think you can specify block size on the backup.

From the manpage.

-c config
.... config is the name of the configuration file, and can
.... contain values for the following parameters:
.... + Number of 1024-byte blocks per record.