Equivalent of IBM Storage Archive SDE 2.4.8.1 (10519)

IBM released IBM Storage Archive 2.4.8.1 (10519) at 1287159. So the LTFS project releases a new version 2.4.8.1

Change Log:

• Linux:

  • Updated libxml2 to version 2.13.8 to address security vulnerability CVE-2025-32415

• Windows:

  • Fixed issue where binaries were crashing when displaying large messages on the console.
  • Auto-upgrade functionality is now enabled; manual uninstallation is no longer required.
  • CMD Tools binaries have been re-included in the LTFS SDE package.

• For problem fixes that were reported in the previous versions:

  • See dce31f8..1287159

Equivalent of IBM Storage Archive SDE 2.4.8.0 (10517)

IBM released IBM Storage Archive 2.4.8.0 (10517) at dce31f8. So the LTFS project releases a new version 2.4.8.0

Change Log:

• For problem fixes that were reported in the previous versions:
  • See 7271446..dce31f8

Equivalent of IBM Storage Archive SDE 2.4.7.1 (10515)

IBM released IBM Storage Archive 2.4.7.1 (10515) at d8c223b. So the LTFS project releases a new version 2.4.7.1

Change Log:

• Fixed the issue where a tape cartridge with a write-permanent error failed to be mounted, displaying
  the error message: "LTFS17285E Failed to search the final index in IP (1)", despite LTFS being capable
  of searching the index on the Data Partition (DP). (#493)

Equivalent of IBM Storage Archive SDE 2.4.7 (10514)

IBM released IBM Storage Archive 2.4.7.0 (10514) at 7271446. So the LTFS project releases a new version 2.4.7.

Change Log:

• For problem fixes that were reported in the previous versions:
  • See 060ccf3..7271446

Equivalent of IBM Storage Archive SDE 2.4.6.2 (10513)

IBM released IBM Storage Archive 2.4.6.2 (10513) at 060ccf3. So the LTFS project releases a new version 2.4.6.2.

Change Log:

• For problem fixes that were reported in the previous versions:
  • See fd41c66..060ccf3

Equivalent of IBM Storage Archive SDE 2.4.6.1 (10511)

IBM released IBM Storage Archive 2.4.6.1 (10511) at fd41c66. So the LTFS project releases new version 2.4.6.1.

Change Log:

• For problem fixes that were reported in the previous versions:
  • See 9ab1dc5..2273268

Equivalent of IBM Storage Archive SDE 2.4.6.0 (10507)

IBM released IBM Storage Archive 2.4.6.0 (10507) at 9ab1dc5. So the LTFS project releases new version 2.4.6.0.

Change Log:

• For problem fixes that were reported in the previous versions:
  • See 486ce60..7d5c5af

Equivalent of IBM Spectrum Archive SDE 2.4.5.0 (10502)

IBM released IBM Spectrum Archive 2.4.5.0 (10502) at 19c3fd3. So the LTFS project releases new version 2.4.5.0.

Change Log:

• For problem fixes that were reported in the previous versions:
  • See 3287850..3b26f03

Equivalent of IBM Spectrum Archive SDE 2.4.4.0 (10470)

IBM released IBM Spectrum Archive 2.4.4.0 (10470) at 3287850. So the LTFS project releases new version 2.4.4.0.

Change Log:

• Support LTO9 drive
• Fixed and improved MAM handling in cases where MAM might not update correctly during write errors,
  so that LTFS correctly searches for the latest index position of the tape for these cases.
• For problem fixes that were reported in the previous versions:
  • See cdf782f..872c18a

Equivalent of IBM Spectrum Archive SDE 2.4.3.1 (10461)

IBM released IBM Spectrum Archive 2.4.3.1 (10461) at aa181ad. So the LTFS project releases new version 2.4.3.1.

Critical fix

IMPORTANT Notice

For the users of LTFS version 2.4.0 or above, it is highly recommended to upgrade the software to version 2.4.3.1 immediately. The problem was fixed into (#233, 303ca43). When the LTFS would truncate the files ion tape unexpectedly when LTFS receives a permanent write error at SCSI LOCATE command before SCSI WRITE command.

The scenario is

1. LTFS tries to write a data block of a file at the end of tape
2. LTFS issues LOCATE command to seek to the end of tape
3. LTFS receives a permanent write error against LOCATE command
4. LTFS looks this permanent write error as a a permanent write error against WRITE command and make error recovery
5. LTFS fetches the current position on the tape (the position is as same as the position before LOCATE command is issued because it fails)
6. LTFS clear all extents larger than current position
7. LTFS tries to seek to the append position of the index partition
8. The file truncation would be completed when this seek is successfully done (At the most cases this seek wouldn't success but we have a few possibility)
9. LTFS would write the current cleaned index on the index partition and the file truncation is completed

Change Log:

• Fix exceeded extent cleaning when a write perm returns against LOCATE before write operation
• For problem fixes that were reported in the previous versions:
  • See aa181ad..1121daa