Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
Using an LTO3 robotic tape library on Linux, is there any way to tell if a tape is at the end of its run by /var/log/messages entries, or via mt or mtx or other requests, or if the tape has a genuine problem? I recently had a hard drive fail on another backup system on a Friday evening, and I wanted to get backup running on it asap. I simply ended up installing the OS (CentOS) from CDs, retyped a shell script I created, and backups were running fine. This was a reason why something like bacula, amanda, etc might be too cumbersome to rebuild in a short period of time. I'd be more than happy to hear argument contrary to this thinking. /var/log/messages shows: Current: sense key: Not Ready Additional sense: Logical unit not ready, operation in progress Error on write filemark The drive is pretty new, and I was doing weekly backups, now doing daily incrementals. How do I tell if the tape is broken, at the end of its reel, or if the drive is dirty? I'm doing incremental backups to two tapes each night, and the other tape worked fine, making me think the "bad" tape either is full or has a physical problem. I tried a rewind and tar xvf but get errors. Thanks for any insights. Scott -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |