Mark K

I have noticed a related (but probably different) issue. I have a .tar archive which contains a sparse file. 7-zip 22.01 (x64, Windows 10) does seem able to unpack it, but it "expands" the sparse file to its full size. By contrast tar.exe in Windows 10 can correctly extract the sparse file (i.e., its on-disk size is less than the file size). >tar --version bsdtar 3.5.2 - libarchive 3.5.2 zlib/1.2.5.f-ipp 7-zip upacks the file to use ~4,000,000,000 bytes on disk. Whereas tar.exe extracts it as a sparse...

I have noticed a related (but probably different) issue. I have a .tar archive which contains a sparse file. 7-zip 22.01 (x64, Windows 10) does seem able to unpack it, but it "expands" the sparse file to its full size. By contrast tar.exe in Windows 10 can correctly extract the sparse file (i.e., its on-disk size is less than the file file). >tar --version bsdtar 3.5.2 - libarchive 3.5.2 zlib/1.2.5.f-ipp 7-zip upacks the file to use ~4,000,000,000 bytes on disk. Whereas tar.exe extracts it as a sparse...

--read-sector: Add option for raw/binary output

--read-sector: Use SAT or other passthrough method if needed (for sg not block device)

Thanks! On the subject of IDENTIFY DEVICE data, is there any chance you'd consider adding the ability to dump the raw binary data? I attached a patch to do that in this feature request. Binary data is useful for other programs rather than having to parse an ASCII hex dump. [sg_sat_identify can dump binary IDENTIFY data, but hdparm probably works in more cases, e.g. with vendor-specific USB-ATA passthrough.]

--Istdin incorrectly byte-swaps (or fails to) hex identify data

Example archive (~84MB): https://www.mediafire.com/?zvskd27ylq7xjaa That's an XZ-compressed tar archive. Decompressing to .tar works fine, but when you open the .tar archive 7-Zip shows a dialog: "Can not open file '[filename]' as archive."

Using --Istdout appends bogus text to the hex dump