Hi,

Ross Boylan wrote:

As detailed in my earlier messages, I have my storage writing to disk
files, and my first attempt failed because I had an invalid volume
name.

I have cancelled the offending jobs (except parts linger on--see
later), fixed (maybe) my label generation, and asked the director to
reload its configuration (I'm not sure if that's a full restart under
the hood or not--this is on Debian).

One important question: Is anything vital running in bacula at the moment? The most effective way to to get everything unstuck is, after all, a /etc/init.d/bacula restart or killall -9 bacula :-)

On the clients with stuck fd too, of course...

Usually, a reload (or reload from inside a console) is not a restart but only triggers reloading of the configuration (this works in the director only!). Usually, the reload will be queued, because (my personal guess without any real knowledge about the source) it might change important data in running or queued jobs.

But, I can't get it unwedged, as seen from bconsole:
...

I also tried issued mount several times, but the device remains
blocked.

It is possible that Job 43 will succeed if it can get through.

I do not want to use label from the console, because it is the
automatic labelling that I need to test (I also don't know if that
would help things).

Understandable. Still, why not simply shutdown bacula and restart it?

The stuck jobs on remote machines will usually time out after 2 hours. If they don't it should be safe to restart their daemons.

Concerning a stuck SD - that's tricky. I managed that myself some times, but it always involved tape devices here. In those cases, there was either a really long timeout necessary (long in computer terms - we're talking about some hours here) or I turned the drive's power off, waited for the kernel to start complaining, turned it on again. After that, the SD recovered quickly.

Any suggestions?

Restart or wait.

Arno

Ross

P.S. I'm not sure why job 41 is still there.  When I try to cancel it
I get the message it is not active.  Status shows it is not active on
the director, but it is active on fd and sd.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to