Re: [Bacula-users] syslog and btape

[Kern S. <ke...@si...>]

On Saturday 30 September 2006 02:09, m listus wrote:
> hi,
> 
> i'm using 1.36.2 on sarge.
> i get this kernel message on dmesg on a per job basis
> i think:
> st0: MTSETDRVBUFFER only allowed for root.

I've now suppressed that in 1.39.23.  The ioctl() will only be done if you are 
running the SD as root.

> 
> i read the "Syslog Errors" section in the tape testing
> chapter, but it's too vague: ". In general, the
> message can be ignored providing you are sure that
> your OS parameters are properly configured as
> described earlier in this manual."
> i read the chapter, and i'm still not sure the OS
> params are right.
> that said it works.
> but i want to know if i need to set some st0 param at
> boot time in an init script. that seems the most
> appropriate. i have an 8mb internal tape buffer, and i
> even don't know which size is set by the kernel.

The tape testing chapter of the manual describes what settings must be made.
If I am not mistaken, it also points out what is "permanent" and what may 
change after rebooting.  Every OS is a bit different in how they handle and 
let the user change the default tape modes.  Fortunately, *most* modern OSes 
start with a default that is compatible with Bacula.

> 
> 2nd point, i've been trying to get the 2nd part of
> "tape testing" chapter to work, that is: fill w/ 2
> tapes.
> all tests work (including fill w/ 1 tape).
> the problem happens when using the 2nd tape.
> this might be a problem becaus i'm using the 'daily,
> weekly, monthly scheme' that uses a daily tape until
> it fills, and the it requests the next one.

Two volume tape "fill" has had its share of bugs (mainly because it takes so 
long to test it).  I think they are mostly resolved in version 1.39.11.