At 12:15 22/10/2002, Charlie Brady wrote:
Some while ago, I reported what I believe is a bug (the same problem under discussion here) in flexbackup processing (TT20020415032). I also have a Seagate Travan 5 drive. I did a bit of analysis with the Mitel support people, including, IIRC, an strace. My understanding is that it is open internally, but that they haven't been able to put resources to it.The rewind cannot be the cause of the problem, since it just puts the tape back to the beginning which is were we expect it to be when we perform a backup. It *might* be a workaround which happens to work, just as the "write a block of zeroes and then rewind" was a workaround which happened to allow IDE tape backup work in the first place(*). The real cause lies elsewhere.
In the meantime, I've recently been trying to resolve this and have been testing the "flexbackup -newtape" option. I've added it via a custom template to the script ahead of the existing steps (right after the path command, in fact) and it has been running OK the past couple of weeks. I'd be interested to learn if this works for others, and also why this might work at all...
Des Dougan
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
