In message <[EMAIL PROTECTED]> you wrote: > > Curious as to why tar worked when btape did not, I found this. For > portability reasons, tar appears to always use a physical block size of > 512 bytes. See > http://www.gnu.org/software/tar/manual/html_section/tar_73.html. Perhaps > that explains the difference in how tar writes to tape versus how btape > writes to tape.
This is a misinterpretation. The physical *tape* block size or record size is a multiple of the 512 byte block size, as determined by the '-b' resp. '--blocking-factor' option. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] People have one thing in common: they are all different. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
