When deleting a pool via bconsole, the volumes of that pool still exists 
in filesystem but are not known anymore to the director and needs to be 
deleted manually. When I use the label <previouslabel> command:

Connecting to Storage daemon daily_storage at 192.168.2.211:9103 ...
Sending label command for Volume "<previouslabel>" Slot 0 ...
3920 Cannot label Volume because it is already labeled: "<previouslabel>"
Label command failed for Volume <previouslabel>.

I wonder if this is by design?
Also all jobs written to volumes of that pool still exists in database 
and are shown on "list jobs". You need to go and delete all jobs of that 
volume by hand. This can be much fun.

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users