Kern Sibbald wrote:
On Monday 07 November 2005 15:15, Julien Cigar wrote:
You think I can ignore the problem ?
When I list media you can see that the tape Weekly-0003 has not been
filled up completely (it was the tape with write errors ...)
Well, that answers the question I had: the drive could not recover from the
error, and it *did* notify Bacula. In principle, Bacula stopped writing when
the tape/drive got the error, so your backup should be good, but personally,
I would be very worried whether the data on the tape was readable or not.
At a minimum, I would start doing Verifys of all my tape jobs to ensure that
the tape can be read -- they are slow, but at least you will know. I would
also try doing a btape "fill" on the tape that got the errors (after ensuring
that all the files are backed up elsewhere). If it fails, I would trash the
tape.
The best solution is to get a DLT or SDLT drive.
If you cannot, one thing that I noticed here with my HP drive is that tapes
from some manufacturers fail all the time, and tapes from others last two
years before failing (under heavy use). For example, if I remember right, I
have no problem with Sony tapes in my drive, but Imation tapes cause me
problems (or vise-versa). I forget because I only use the drive for testing,
and I frequently need to throw out tapes. The only way you can know is to
try tapes from different manufacturers in your drive, and the only thing I
can say for sure, is that for my drive, there is a lot of difference between
tapes from different manufacturers.
The sense data kernel errors are what happens when a tape is manually
ejected from the drive while a process has the st driver opened. I
don't
believe the tape was ejected, but the drive did or the st driver did.
Either the tape is bad (most likely), the drive is broken (maybe),
there is a scsi hardware problem (perhaps), the drive's firmware is
badly broken (not likely), or the st driver is broken (very unlikely).
I agree, the first thing to suspect is the tapes. So if there are any
known good tapes that have been used sucessfully in the recent past,
try one of them. If it still works without generating errors, then the
tapes, new or not, are bad. If the same errors are generated with a
known good tape, then there is almost certainly a hardware problem.
Eliminate the possibility of a scsi hardware problem by trying a
different scsi cable, removing all other devices (if any) from that
scsi cable, and trying a different scsi terminator. If possible, try
another scsi port, preferably on another scsi controller. If it still
doesn't work, then the problem is almost certainly that the drive is
broken.
*list media
Pool: WeeklyFullBackupPool
+---------+-------------+-----------+-------------+----------+-------------
-+---------+------+-----------+-----------+---------------------+
| MediaId | VolumeName | VolStatus | VolBytes | VolFiles |
VolRetention | Recycle | Slot | InChanger | MediaType |
LastWritten |
+---------+-------------+-----------+-------------+----------+-------------
-+---------+------+-----------+-----------+---------------------+
| 1 | Weekly-0001 | Full | 71563809646 | 73 |
2592000 | 1 | 0 | 0 | DAT | 2005-10-28
10:38:32 |
| 2 | Weekly-0002 | Full | 79126531739 | 79 |
2592000 | 1 | 0 | 0 | DAT | 2005-10-30
11:28:16 |
| 3 | Weekly-0003 | Full | 45914843881 | 47 |
2592000 | 1 | 0 | 0 | DAT | 2005-11-07
06:01:46 |
| 4 | Weekly-0004 | Full | 81241762264 | 81 |
2592000 | 1 | 0 | 0 | DAT | 2005-11-07
12:17:00 |
However, the jobs terminate with a "Backup OK" termination ... strange
Kern Sibbald wrote:
On Monday 07 November 2005 09:04, Julien Cigar wrote:
Hello,
I writed a mail some weeks ago for a problem with my Sony drive (write
errors).
The drive is a Sony SDX-500C on a Adaptec 2940 Ultra SCSI.
Someone told me to upgrade the bios of the drive, which I did. It worked
fine for a week, but now I'm still having writing error messages :
Nov 7 06:01:46 localhost kernel: st0: Error with sense data: <6>st0:
Current: sense key: Medium Error
Nov 7 06:01:46 localhost kernel: Additional sense: Write append
error Nov 7 06:01:46 localhost kernel: Info fld=0xfc00
Nov 7 06:01:46 localhost kernel: st0: Error with sense data: <6>st0:
Current: sense key: Medium Error
Nov 7 06:01:46 localhost kernel: Additional sense: Write append
error Nov 7 06:01:46 localhost kernel: Info fld=0x1
Nov 7 08:42:26 localhost kernel: st0: Error with sense data: <6>st0:
Current: sense key: Unit Attention
Nov 7 08:42:26 localhost kernel: Additional sense: Not ready to
ready change, medium may have changed
Nov 7 08:47:37 localhost kernel: st0: MTSETDRVBUFFER only allowed for
root.
What happens is, it backs up perfectly fine for a while backup,
restoring from tape works too! Then all of a sudden it starts giving an
error ...
I don't think it's tape related, the tapes are new and the problem
occurs only randomly ...
I've checked the cable too
Any idea welcomed ...
All the errors at 06:01 appear to me to be typical write errors that one
often gets on DDS tapes. From what I see, the drive recovered and
continued. I doubt that Bacula was even aware of the problem -- though
you can check in the Job report.
The errors are 8:42 are a bit worrysome. I would attempt to correlate them
with what Bacula was doing. It may only be that Bacula asked for a new
tape and tried to read while there was nothing in the drive, or it may be
some real failure.
The "error" at 8:47 is apparently after you restarted the FD. It attempts
to set the tape to variable tape format, and your kernel forbids the
request (ioctl) if the SD is not being run as root. This can be ignored
if your tape drive mode is set properly before starting the SD.
----------
Here's the output of /proc/scsi/scsi :
phoenix:/home/jcigar# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SONY Model: SDX-500C Rev: 0204
Type: Sequential-Access ANSI SCSI revision: 02
----------
Here's the output of /proc/scsi/aic7xxx/0 :
phoenix:/home/jcigar# cat /proc/scsi/aic7xxx/0
Adaptec AIC7xxx driver version: 6.2.36
Adaptec 2940 Ultra SCSI adapter
aic7880: Ultra Wide Channel A, SCSI Id=0, 16/253 SCBs
Allocated SCBs: 4, SG List Length: 128
Serial EEPROM:
0x0238 0x0238 0x0238 0x0238 0x0238 0x0238 0x0238 0x0238
0x0238 0x0238 0x0238 0x0238 0x0238 0x0238 0x0238 0x0238
0x18b6 0x005d 0x2800 0x0010 0xff00 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x00ff 0x6499
Target 0 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 1 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Goal: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Curr: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Channel A Target 1 Lun 0 Settings
Commands Queued 3051621
Commands Active 0
Command Openings 1
Max Tagged Openings 0
Device Queue Frozen Count 0
Target 2 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 3 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 4 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 5 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 6 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 7 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 8 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 9 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 10 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 11 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 12 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 13 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 14 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
Target 15 Negotiation Settings
User: 20.000MB/s transfers (10.000MHz, offset 127, 16bit)
-------------------------------------------------------
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
-------------------------------------------------------
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
|
