Hi,

On 2/28/2007 5:12 PM, [EMAIL PROTECTED] wrote:
> Hello,
> 
> I am having an issue with bacula 1.38.11 on a Solaris 2.9 system with a
> Qualstar RLS 8236 LTO-2 autochanger. I have had this setup working for
> over a year and a half. There seems to be a problem with bacula getting
> confused on which pool a tape belongs to here is a snip of the status
> storage:
> 
> Device status:
> Autochanger "Autochanger-0" with devices:
>    "LTO-0" (/dev/rmt/0cbn)
>    "LTO-1" (/dev/rmt/1cbn)
> Device "FileStorage" (/tmp) is not open or does not exist.
> Device "LTO-0" (/dev/rmt/0cbn) is mounted with Volume="Daily01-0004"
> Pool="Daily01"
>     Slot 1 is loaded in drive 0.
>     Total Bytes Read=64,512 Blocks Read=1 Bytes/block=64,512
>     Positioned at File=0 Block=0
> Device "LTO-1" (/dev/rmt/1cbn) is mounted with Volume="Daily02-0004"
> Pool="Daily01"
>     Slot 6 is loaded in drive 1.
>     Total Bytes Read=64,512 Blocks Read=1 Bytes/block=64,512
>     Positioned at File=0 Block=0
> ====
> 
> In Use Volume status:
> Daily01-0004 on device "LTO-0" (/dev/rmt/0cbn)
> Daily02-0004 on device "LTO-1" (/dev/rmt/1cbn)
> ====
> 
> The status storage reports the pool for volume Daily02-0004 as being
> Daily01, but a list media shows the volume is the Daily02 pool which is
> the correct pool.
> 
>>From a list media pool=Daily02:
> +---------+--------------+-----------+-----------------+----------+-----
> ---------+---------+------+-----------+-----------+---------------------
> +
> | MediaId | VolumeName   | VolStatus | VolBytes        | VolFiles |
> VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten
> |
> +---------+--------------+-----------+-----------------+----------+-----
> ---------+---------+------+-----------+-----------+---------------------
> +
> |      34 | Daily02-0001 | Used      | 123,469,545,497 |      143 |
> 5,184,000 |       1 |   18 |         1 | LTO-2     | 2007-01-13 04:19:14
> |
> |      36 | Daily02-0002 | Used      | 134,669,297,962 |      154 |
> 5,184,000 |       1 |    7 |         1 | LTO-2     | 2007-02-06 03:18:23
> |
> |      38 | Daily02-0003 | Used      | 157,600,113,825 |      171 |
> 5,184,000 |       1 |   20 |         1 | LTO-2     | 2007-02-22 03:26:51
> |
> |      40 | Daily02-0004 | Append    |   9,882,711,009 |       16 |
> 5,184,000 |       1 |    6 |         1 | LTO-2     | 2007-02-28 14:02:35
> |
> +---------+--------------+-----------+-----------------+----------+-----
> ---------+---------+------+-----------+-----------+---------------------
> +
> *
> 
> I only have one bacula catalog.
> 
> Why does bacula think the volume Daily02-0004 is in the Daily01 pool?

Looks like a bug to me.

> Has anyone run into a similar situation?

Not me, but I understand there are some improvements in the autochanger 
handling, especially for devices with more than one drive, in the 2.0 code.

> I believe because of this problem, I needed to unmount and remount the
> volumes to get bacula to finish the backup jobs today.

That sounds quite reasonable.

...
> Here is my autochanger and device setup:
... which looks perfectly ok to me...

...


> Please let me know if you need more information.

I see two possible ways to continue:
- Try to make the problem reproducible. That might mean to spend lots of 
time, perhaps without success. Then report this as a bug at 
bugs.bacula.org - the information you gave seems quite clear to me. 
Though I can't tell for sure, I could imagine Kern fixing the problem 
even after he's mainly working at version 2 now (probably as a back-port 
of a patch for the current version).
- Upgrade to version 2. Even if this doesn't necessarily fix this 
particular issue (and keep in mind I did not check at bugs.bacula.org if 
something like your bug has been reported yet :-) the chances that it 
will be fixed once you reported it at bugs.bacula.org are a little 
better, I think.

I assume that this probem doesn't hit you very often, right? In that 
case, I'd recommend to simply continue using 1.38.11 and preparing the 
step to version 2 (which is not a really difficult one).

When you can reproduce the problem, report it at bugs.bacula.org.

Move to Bacula 2.0 when it suits you, and see if this problem persists. 
If it does, you should report it again as soon as possible to get this 
fixed.

> Thank you,

Hope this helps,

Arno

> Tom.
> ----
> Thomas Boyda <[EMAIL PROTECTED]>
> Consultant Proxicom, Inc.
> http://www.proxicom.com
> Phone: 276-739-2314
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bacula-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to