-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A great file app that I am not able to make it work #6
Comments
By the way, it would be great if we could have more documentation on how to initiate the app in Ubuntu. |
Autoloader is not tested, but you can add some corresponding commands to those scripts under the |
I have a similar problem- this is not working with IBM HH LT05 drive, the IBM LTFS driver version 2.5.0.0. Installed as root. OS is openSUSE Leap 15.5. The drive works from the command line - I can mount it from /dev/sg7 and copy files to it - but installing and following the readme didn't yield a functional system, as follows:
Thoughts? |
@patrickfitz /dev/tape/by-id/scsi-HUJ0000000 kinds of path or sg / nst path all can work. I use /dev/tape/by-id/xxx because I have multiple drives, and the sg number will change after reboot. You could use FILE and RESTORE tabs will have files when you finish your first BACKUP job, and those files in the backup job will be put into the FILE database (aks library). The BACKUP tab shows the path that is specified in the config.yaml. If you didn't config it, as default, it will show the root path of this service. In conclusion, you should consider editing config.yaml before using. |
If you're having an issue were the load tape dialog doesn't close check the barcode you're entering. LTO barcodes are at max 8 long and if you enter something longer the page errors and doesn't close the window. Once the window closes you'll see it start to interact with the drive. |
@swildig @patrickfitz I added error popups recently, you guys can update to the newest version to check which step went wrong. |
It is my understanding that the DB only gets populated at Backup time. Why if we already moved data to tapes and we want to load the list of content in YATM? Sounds like we have to restore to disk and then back up again using YATM? Tried to run a backup and when I click on "Submit" on the tape job, nothing happens :( and nothing in logs except for first startup row: time="2024-03-23T13:36:01Z" level=info msg="read config success, conf= '&{Domain:http://xxx:8080 Listen:xxxx:8080 DebugListen:xxx:8081 Database:{Dialect:sqlite DSN:./tapes.db} Paths:{Work:./ Source:./ Target:./} TapeDevices:[/dev/tape/by-id/scsi-HU1229P78K /dev/tape/by-id/scsi-HU1220P79Y] Scripts:{Encrypt:./scripts/encrypt Mkfs:./scripts/mkfs Mount:./scripts/mount Umount:./scripts/umount ReadInfo:./scripts/readinfo}}'" using openltfs-2.4-stable https://github.com/LinearTapeFileSystem/ltfs/tree/v2.4-stable If I manually load tapes, here's what I get from yatm-lto-info (seeams like it's using only one of the 2 tape drives though): Drive information: |
I want to say it's an excellent idea for the author to attempt an open-source LTFS tool since there is a great need for people like us who don't want to use proprietary software with their tape system. I am having issues installing this app in Ubuntu (22.04.1 LTS). The following are the problems/questions I have during my installation:
Hardware used (they work great in Windows Server 2022)
Much appreciated for the author for his hard work!
The text was updated successfully, but these errors were encountered: