I have a Quantum SDLT tape drive that seems to have changed behavior recently, and I don't understand why. In the past, our developers were able to write a file, then issue a "mt bsf 2" command to back up the tape so that they could read back the file that they had just written.
Following a reboot, this no longer works. They now get an immediate EOF condition after an "mt bsf 2", and need to use an "mt bsfm 2" command to backspace two filemarks and then skip forward over the next filemark to get the tape positioned as used to happen in response to an "mt bsf 2" command. My first thought was that this was caused by a change in the new Linux 2.6 kernel version that went into effect at the reboot, but I see the same behavior with all kernels that have ever been installed. The mt command itself hasn't changed since the OS was installed, and none of the mt setoption commands seem like they could cause this change in behavior. This change in behavior isn't causing any problems for Bacula, and since the new behavior matches what is documented in the mt man page I can't report this as a bug, but the inexplicable change in behavior bothers me. I'd rest easier if I knew why this change happened. Has anyone seem anything like this, or know what might cause it or where I could look to investigate further? Thanks for any suggestions. -- John Kodis. ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
