ltfs
ltfs copied to clipboard
fix/: change LTOA to LTO10
LTOA to LTO10
This pull request includes following changes or fixes.
- Fix
Description
Change LTOA to LTO10
Type of change
- Refactoring
Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [x] I have confirmed my fix is effective or that my feature works
Hello @Magic-Kowel Is there a specific reason to do this change? For what I can assume it seems to be a decision for maintain the decimal way to name the LTO10 generation instead of adopting the already merged hexadecimal way, but why? Is there any advantage? Thank you in advance for the response!
Successful integration test of LE and LTFS in the file backend environment.
branch LE and ltfs
[root@atreus oss]# git branch
* LTO10_Support
fix/strdup-memory-check
master
v2.4-stable
v2.4.8-windows-support
[root@atreus oss]# cd ..
[root@atreus ltfs-sde]# cd ..
[root@atreus ltfs]# git branch
LTO10-support
LTOA_Support
fix/strdup-memory-check
gitmodules-fix
main
master
* release/v2.4.8.1
Commands
leadm drive list
Serial Device Model Status Tape
VDRIVE0000 - [ULTRIUM-TD8] Unavailable -
VDRIVE0001 - [ULTRIUM-TD8] Unavailable -
VDRIVE0002 - [ULTRIUM-TD8] Unavailable -
VDRIVE0003 - [ULTRIUM-TD8] Unavailable -
[root@atreus oss]# leadm tape list
Barcode Location Used Avail Use% Severity(Status)
V00000L8 DRIVE - - - WARNING(INACCESSIBLE)
V00001L8 SLOT - - - INFO(NEED_ASSIGN)