Bug ID 639575: Using libtar with files larger than 2 GB will create an unusable tarball

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.5.6, 11.5.5, 11.5.4

Fixed In:
13.0.0 HF1, 12.1.4, 11.6.5.1, 11.5.7

Opened: Jan 16, 2017
Severity: 3-Major
Related AskF5 Article:
K63042400

Symptoms

Programs such as qkview create a .tar file (tarball) using libtar. If any of the files collected are greater than 2 GB, the output tar file cannot be read by /bin/tar. This occurs due to a limitation of the file compression library employed by qkview command; the system cannot collect files larger than 2 GB in size in a Qkview. The qkview command may generate output that iHealth cannot parse, and that the tar command cannot extract.

Impact

No qkview diagnostics file is created. Although you can extract the qkview tarball using /usr/bin/libtar, the file will be a zero-length file. Cannot submit a qkview to iHealth for analysis. Other applications using libtar will produce invalid tar files.

Conditions

-- The file collected via libtar (e.g., by qkview or other program dynamically linking with /usr/lib/libtar-1.2.11) is greater than 2 GB. -- A 2 GB or larger file exists in a directory that qkview normally collects.

Workaround

Remove the file larger than 2 GB from the system prior to running qkview or other program that uses libtar.

Fix Information

With the fix to third party software, libtar, programs using libtar no longer create an unusable tarball when dealing with files larger than 2 GB.

Behavior Change