[
https://issues.apache.org/jira/browse/COMPRESS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924943#comment-16924943
]
Stefan Bodewig commented on COMPRESS-468:
-----------------------------------------
I don't think this is as clear as you state it. Looking at the tar manpage for
FreeBSD ( [https://www.unix.com/man-page/FreeBSD/1/tar/] ) you can see
{quote} *_-b_*
blocksize,
*_--block-size_*
blocksize Specify the block size, in 512-byte records, for tape drive I/O. As a
rule, this argument is only needed when reading from or writ- ing to tape
drives, and usually not even then as the default block size of 20 records
(10240 bytes) is very common.{quote}
Here you can see that a block consists of records, each record has 512 bytes
and each block has 20 records of 512 bytes by default. I think GNU tar and
POSIX tar are using different terminology and we have been using it the way we
do for about twenty years now :)
> Tar block and record size terminology
> -------------------------------------
>
> Key: COMPRESS-468
> URL: https://issues.apache.org/jira/browse/COMPRESS-468
> Project: Commons Compress
> Issue Type: Bug
> Components: Documentation
> Reporter: Yuval Turgeman
> Priority: Minor
>
> According to
> [tar|https://www.gnu.org/software/tar/manual/html_node/Blocking.html] the
> definition of a block is 512 bytes, and a record is a collections of blocks
> that will be written in a single write. In the commons compress code and
> docs, it is mentioned that a record has a fixed size of 512 bytes, and a
> block contains several records, which is the other way around.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
