I'm in the process of upgrading from 2.5.0p2 to 2.6.1p2 and from an SAIT
drive to an LTO-4 drive on the backup server (CentOS 5.4, 64-bit). This
is the second time I've seen amcheck knock my tape drive offline.
Here's the scenario that led to the problem:
I successfully ran an amdump
Your SCSI HBA ran into a failure on the SCSI bus, and went through its
usual recovery steps - try to reset the failed target, try to abort,
offline the device, try to reset the failed bus, and try to reset the
failed HBA. It looks like it stopped after the third step, leaving
your /dev/st1
In attached version:
I scanned the list for comments after Charles' posting, and I think I
got everything in this version.
Overall, I got rid of redundant/unnecessary stuff, cleaned up some
language, and added some things that were missing.
I would also suggest that we make this file
We don't check or manipulate the archive bit of the file. We check the
modified time of the file with respect to last backup (full or incremental)
to decide if the file should be included in the incremental backup or not.
This is tracked in a MySQL catalog on the client
Paddy
On Tue, Dec 22,
