Hello,
On Tuesday 09 March 2010 23:59:46 Jakub Witkowski wrote:
> Hello,
>
> Is there any formal specification of fd-to-sd and fd-to-dir protocol
> specification apart from the code itself? I'm willing to invest some time
> into writing proper AFS backend for Bacula, but frankly I'd prefer startin
On 3/9/2010 5:59 PM, Jakub Witkowski wrote:
> Hello,
>
> Is there any formal specification of fd-to-sd and fd-to-dir protocol
> specification apart from the code itself? I'm willing to invest some time
> into writing proper AFS backend for Bacula, but frankly I'd prefer starting
> with zero code du
Hello,
Is there any formal specification of fd-to-sd and fd-to-dir protocol
specification apart from the code itself? I'm willing to invest some time
into writing proper AFS backend for Bacula, but frankly I'd prefer starting
with zero code due to both very different way AFS does things as well as
Maybe its a firewire problem. Is there any way to test it with SCSI ?
On 3/9/2010 11:05 AM, David Koski wrote:
> Thank you Kern. I'll dig into it some more. For the list, it is Linux and
> firewire with Bacula 5.0.0-5 Debian platform and package.
>
> Regards,
> David Koski
> da...@kosmosisland.
Thank you Kern. I'll dig into it some more. For the list, it is Linux and
firewire with Bacula 5.0.0-5 Debian platform and package.
Regards,
David Koski
da...@kosmosisland.com
On Tuesday 09 March 2010, Kern Sibbald wrote:
> Hello,
>
> This means that your tape drive parameters are not properly
Hello,
On Tuesday 09 March 2010 12:47:33 JanJaap Scholing wrote:
> Hi Kern,
>
> I reported the problem (with traceback) in Mantis (0001527).
Yes, I saw. Thanks. As best I can tell it is definitely deadlocked.
Eric is going to show you how to enable the lock manager code later today.
Then w
Hi Kern,
I reported the problem (with traceback) in Mantis (0001527).
Thanks.
Regards,
Jan Jaap
>
> On Monday 08 March 2010 12:20:04 JanJaap Scholing wrote:
> > Hi,
> >
> > My bacula-sd is deadlocking during copy jobs.
> >
> > Version 5.0.1
> > compile option: --with-readline=/usr/includ
Hello,
This means that your tape drive parameters are not properly set. You have
never specified what OS and version you are using. This is not the normal
kinds of problems we see on Linux systems.
Unfortunately, as I previously mentioned, you will need to do this yourself or
get professional
