bugGNU tar - Bugs: bug #66704, Inconsitence in documentation...

 
 

bug #66704: Inconsitence in documentation about blocking factor

Submitter:  emontnemery <emontnemery>
Submitted:  Fri 24 Jan 2025 07:16:05 AM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  gray
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 14 Mar 2025 07:12:08 AM UTC, comment #1: 

Fixed in commit 55ecb283. Thank you.

Sergey Poznyakoff <gray>
Group administrator
Fri 24 Jan 2025 07:16:05 AM UTC, original submission:  

The tar manual states, in the section on blocking:

> When writing to tapes, tar writes the contents of the archive in chunks known as records. To change the default blocking factor, use the ‘--blocking-factor=512-size’ (‘-b 512-size’) option. Each record will then be composed of 512-size blocks. (Each tar block is 512 bytes. See section Basic Tar Format.) Each file written to the archive uses at least one full record. As a result, using a larger record size can result in more wasted space for small files.


However, it doesn't seem to be the case that each file in the archive uses a full record, it's only the archive itself which is ensured to use an integer number of records. Individual files are only guaranteed to use an integer number of blocks.


emontnemery <emontnemery>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gray (Posted a comment)
  • -email is unavailable- added by emontnemery (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2025-03-14 gray StatusNone Fixed
        Assigned toNone gray
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.14-430a.
    Corresponding source code