- Based on fixes which will be included in 0.18.12 (when released)
- The 0.19 branch will be to develop the idea of a 'Personality Modules' which will be a 'plugin' style module per device type.
Currently, IBM LTO4, LTO5, IBM 03592, STK T10K and AIT are partially implemented.
No change to the kernel module is required if you already have the 0.18-11 release installed.
Lightly tested with NetBackup 6.5.6 and NetBackup 7.0.
Yes, the library module will also contain a personality module..
Most people are more concerned with drive type emulation rather than the library (once they find a library type that works for them/their backup application). So the tape drives are first off the list.
I'm planning on the whole '0.19' branch as being a stepping stone and incremental steps for the introduction & implementation of the personality module idea.
I'll attempt to keep each '0.19-XX' release functional..
Please note: I am after any feedback on change of behaviour.
I have only implemented 'personality modules' for the following drive types:
STK T10000A and T10000B
IBM 03592 J1A, E05 and E06
Mark, any chance for a quick patch to include LTO-1 in new personality modules so I can test with TSM. As you are maybe aware, TSM does not like anything other than LTO-1 if using IBM Library and and T10000A, T10000B if using STK .. Issue is still pending See Here.. I have already have a setup running using LTO-1 and wanted to upgrade to 0.19-0Beta release and still keep LTO-1 for now.
loading a tape works. Then I wrote data to an empty tape, looks to be working. Rewind tape and tried to read it:
[root@orange ~]# mt -f /dev/nst0 rewind
[root@orange ~]# tar tvzf /dev/nst0
tar: /dev/nst0: Cannot read: Cannot allocate memory
tar: At beginning of tape, quitting now
tar: Error is not recoverable: exiting now
gzip: stdin: unexpected end of file
tar: Child returned status 2
tar: Exiting with failure status due to previous errors
I am a bit worried about the "Cannot allocate memory" error.
mtx -f /dev/changer unload
vtltape: processMessageQ: Q snd_id 10 msg : unload
vtltape: updateMAM: updateMAM(0)
You have new mail in /var/spool/mail/root
All this done with:
loading mhvtl kernel module and starting all executables by hand: