Describe the bug
We are using a BDT library with an LTO-9 drive and LTFS version 2.4.5.1.
When the tape is nearly full, we mount it twice.
During the first mount (generation 155), the cartridge is mounted as read-only.
`
`
Nine minutes later, we mount the tape again. This time, we observe that the tape is marked with the "index-dirty" flag.
`
`
After this second mount, the tape becomes unreadable until it is rolled back to generation 155.
Our question is:
Why is the tape not mounted as read-only during the second mount?
We need the tape to remain readable at all times, especially when it is full, since we always need to read data from full tapes.
Is this expected LTFS behavior, or could this be a bug?
Describe the bug
We are using a BDT library with an LTO-9 drive and LTFS version 2.4.5.1.
When the tape is nearly full, we mount it twice.
During the first mount (generation 155), the cartridge is mounted as read-only.
`
`
Nine minutes later, we mount the tape again. This time, we observe that the tape is marked with the "index-dirty" flag.
`
`
After this second mount, the tape becomes unreadable until it is rolled back to generation 155.
Our question is:
Why is the tape not mounted as read-only during the second mount?
We need the tape to remain readable at all times, especially when it is full, since we always need to read data from full tapes.
Is this expected LTFS behavior, or could this be a bug?