Bacula-users

[Bacula-users] Offline On Unmount causing write errors - huh? (was: btape test vs. Offline On Unmount)

2012-03-21 07:10:53
Subject: [Bacula-users] Offline On Unmount causing write errors - huh? (was: btape test vs. Offline On Unmount)
From: Tilman Schmidt <t.schmidt AT phoenixsoftware DOT de>
To: bacula-users AT lists.sourceforge DOT net
Date: Wed, 21 Mar 2012 12:09:00 +0100
On 17.03.2012 01:00, /me wrote:
> A system I manage, running openSUSE 11.4 x86_64 with vanilla kernel
> 3.2.8, uses Bacula 5.0.2 for backing up to a Tandberg TS400 standalone
> LTO-2 drive connected to an Adaptec 29160 SCSI Adapter, so far using
> LTO-1 tape cartridges as the backup volume doesn't require LTO-2 ones yet.
> 
> Recently I added the line
> 
>  Offline On Unmount = yes;
> 
> to the Device resource in bacula-sd.conf since I read on this list that
> this is supposed to work alright now. Since then, backups reaching the
> end of a tape have reported
> 
> --------8<--------8<--------8<--------8<--------8<--------8<--------8<--------
> 13-Mar 11:06 xenon-sd JobId 333: Error: block.c:577 Write error at
> 19:34967 on d
> evice "LTO-2" (/dev/nst0). ERR=Input/output error.
> 13-Mar 11:06 xenon-sd JobId 333: Error: Error writing final EOF to tape.
> This Volume may not be readable.
> dev.c:1745 ioctl MTWEOF error on "LTO-2" (/dev/nst0). ERR=Input/output
> error.
> 13-Mar 11:06 xenon-sd JobId 333: End of medium on Volume "p042-1"
> Bytes=59,254,594,560 Blocks=918,504 at 13-Mar-2012 11:06.
> --------8<--------8<--------8<--------8<--------8<--------8<--------8<--------

I have now removed the Offline On Unmount option again, and the
errors are gone. So there's something fishy with that option.

The failure above was accompanied by these kernel messages:

Mar 13 11:06:43 xenon kernel: [981814.742648] st0: Sense Key : Medium
Error [current]
Mar 13 11:06:43 xenon kernel: [981814.742677] Info fld=0xfc00
Mar 13 11:06:43 xenon kernel: [981814.742688] st0: Add. Sense: Excessive
write errors
Mar 13 11:06:43 xenon kernel: [981814.762965] st0: Sense Key : Medium
Error [current]
Mar 13 11:06:43 xenon kernel: [981814.762987] Info fld=0xfc00
Mar 13 11:06:43 xenon kernel: [981814.762997] st0: Add. Sense: Excessive
write errors
Mar 13 11:06:43 xenon kernel: [981814.783640] st0: Sense Key : Medium
Error [current]
Mar 13 11:06:43 xenon kernel: [981814.783662] Info fld=0xfc00
Mar 13 11:06:43 xenon kernel: [981814.783672] st0: Add. Sense: Excessive
write errors
Mar 13 11:06:43 xenon kernel: [981814.803884] st0: Sense Key : Medium
Error [current]
Mar 13 11:06:43 xenon kernel: [981814.803906] Info fld=0xfc00
Mar 13 11:06:43 xenon kernel: [981814.803916] st0: Add. Sense: Excessive
write errors
Mar 13 11:06:43 xenon kernel: [981814.864753] st0: Sense Key : Medium
Error [current]
Mar 13 11:06:43 xenon kernel: [981814.864778] Info fld=0x1
Mar 13 11:06:43 xenon kernel: [981814.864788] st0: Add. Sense: Excessive
write errors

Since I removed the Offline On Unmount option, there wasn't a
single "st0: Sense Key" message anymore.

Initially I suspected that things would go wrong once the end of
a tape is reached, but the very tape "p042-1" that errored out at
59,254,594,560 bytes above has now accepted the exact same fileset
with 62,892,490,752 bytes without an error.

I am at a loss how to explain that. Why would Offline On Unmount
affect write operations in such a way? Is the drive to be blamed?
Or is it a bug in the storage daemon?

-- 
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>