> For the complete documentation index, see [llms.txt](https://docs.nodeum.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nodeum.io/data-archiving/hybrid-storage-management/tape-library-management/tape-writing-format-ltfs.md).

# Tape Writing Format : LTFS

Nodeum uses the LTFS open format to write data on magnetic tapes. The LTFS format (Linear Tape File System) is a format supported by the drive and tape library manufacturers which are the founders of the LTO Ultrium consortium. This format has existed since the LTO-5 generation. It offers the unique feature to store both data and index data on tape.

A tape written with the LTFS format can be read independently of any storage system and offers a file system to access the data written on that tape. The LTFS drivers for any kind of operating system can read the index and then execute functions like copy, update or delete. It is also possible to use a graphical interface for features like a simple drag and drop.

Unlike tapes generated by backup software, LTFS tapes can be removed from the appliance, shared and stored. And, because they are stored following an open format under a common standard, other divisions, customers, partners or workgroups can easily access data without having to purchase specialized hardware or additional software.

Nodeum is listed as one of the LTFS Partners. Moreover, it is important to know that Nodeum has been certified as a LTFS certified appliance by the LTO consortium:  

{% embed url="<http://www.lto.org/technology/ltfs/ltfs-compliance-verification/>" %}

###


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nodeum.io/data-archiving/hybrid-storage-management/tape-library-management/tape-writing-format-ltfs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.