Hi all,
a have a bacula server running on Dell T710 server with a IBM ULTRIUM-HH4
tape drive.
Frequently (more than one time a month) the backups has failed with a error
6 on tape drive.
Reading the IBM documentation a found a table what indicates a *write *error,
but both the tape drive and the tapes was changed and problems persists.
The value present on /proc/sys/kernel/hung_task_timeout_secs is 120, that
indicates a 120s for timeout. I dont think this will solve this problem,
120s for timeout is sufficent, is not?
Also, I dont know if this timeout is the cause of effect of the tape write
error.
Anyone can help me?
*Erros on bacula logs*
10-Set 13:00 jupiter.venezanet.com.br-dir JobId 1134: Start Backup JobId
1134, Job=Backup-ORAPRODLOGS.2010-09-10_13.00.00_02
10-Set 13:00 jupiter.venezanet.com.br-dir JobId 1134: Using Device "LTO-4"
10-Set 13:00 pe6800-fd JobId 1134: DIR and FD clocks differ by 27 seconds,
FD automatically compensating.
10-Set 13:00 jupiter.venezanet.com.br-sd JobId 1134: Volume "Scratch02"
previously written, moving to end of data.
10-Set 13:13 jupiter.venezanet.com.br-sd JobId 1134:* Error: Unable to
position to end of data on device "LTO-4" (/dev/nst0): ERR=dev.c:956 ioctl
MTEOM error on "LTO-4" (/dev/nst0). ERR=Erro de entrada/sa<C3><AD>da.*
10-Set 13:13 jupiter.venezanet.com.br-sd JobId 1134: Marking Volume
"Scratch02" in Error in Catalog.
10-Set 13:14 jupiter.venezanet.com.br-sd JobId 1134: Please mount Volume
"Scratch01" or label a new one for:
Job: Backup-ORAPRODLOGS.2010-09-10_13.00.00_02
Storage: "LTO-4" (/dev/nst0)
Pool: Scratch
Media type: LTO-4
*Messages on /var/log/messages*
Sep 10 13:03:53 jupiter kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 10 13:03:53 jupiter kernel: bacula-sd D ffffffff80150462 0
7243 1 7244 7216 (NOTLB)
Sep 10 13:03:53 jupiter kernel: ffff8101b54edc58 0000000000000082
0000000000000001 ffff810045db37d8
Sep 10 13:03:53 jupiter kernel: ffff810c7f3658e8 0000000000000008
ffff81067afd2820 ffff810116eea100
Sep 10 13:03:53 jupiter kernel: 00000258a56373f1 0000000000014fd0
ffff81067afd2a08 000000078807aa5a
Sep 10 13:03:53 jupiter kernel: Call Trace:
Sep 10 13:03:53 jupiter kernel: [<ffffffff80063167>]
wait_for_completion+0x79/0xa2
Sep 10 13:03:53 jupiter kernel: [<ffffffff8008d087>]
default_wake_function+0x0/0xe
Sep 10 13:03:53 jupiter kernel: [<ffffffff88290e85>]
:st:st_do_scsi+0x1f4/0x221
Sep 10 13:03:53 jupiter kernel: [<ffffffff88291994>]
:st:st_int_ioctl+0x5f2/0x92b
Sep 10 13:03:53 jupiter kernel: [<ffffffff80007691>]
find_get_page+0x21/0x51
Sep 10 13:03:53 jupiter kernel: [<ffffffff88291743>]
:st:st_int_ioctl+0x3a1/0x92b
Sep 10 13:03:53 jupiter kernel: [<ffffffff80008d55>]
__handle_mm_fault+0x5f2/0xfaa
Sep 10 13:03:53 jupiter kernel: [<ffffffff88293aba>]
:st:st_ioctl+0xaa5/0xe1f
Sep 10 13:03:53 jupiter kernel: [<ffffffff80066b88>]
do_page_fault+0x4fe/0x874
Sep 10 13:03:53 jupiter kernel: [<ffffffff800a0abe>]
autoremove_wake_function+0x0/0x2e
Sep 10 13:03:53 jupiter kernel: [<ffffffff80042175>] do_ioctl+0x55/0x6b
Sep 10 13:03:53 jupiter kernel: [<ffffffff8003018e>] vfs_ioctl+0x457/0x4b9
Sep 10 13:03:53 jupiter kernel: [<ffffffff800b76a6>]
audit_syscall_entry+0x180/0x1b3
Sep 10 13:03:53 jupiter kernel: [<ffffffff8004c870>] sys_ioctl+0x59/0x78
Sep 10 13:03:53 jupiter kernel: [<ffffffff8005d28d>] tracesys+0xd5/0xe0
Sep 10 13:03:53 jupiter kernel:
Kleber
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
