[Bacula-bugs] [bacula 0000398]: Shared working dir causes problems with large restores

[<bac...@li...>]

The following bug has been CLOSED
======================================================================
http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000398
======================================================================
Reported By:                ttoomey
Assigned To:                
======================================================================
Project:                    bacula
Bug ID:                     398
Category:                   Storage Daemon
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
======================================================================
Date Submitted:             08-04-2005 10:22 PDT
Last Modified:              08-04-2005 15:05 PDT
======================================================================
Summary:                    Shared working dir causes problems with large restores
Description: 
During large restores using option 5 in bconsole, some files are corrupted.
In addition, really big restores (> 200 GB) fail to run and cause the SD to
segfault. This happens only when the FD shares a working directory with the
SD/DIR.

Note: we are using the mysql backend. Our db is aprox 1.5 GB.
======================================================================

----------------------------------------------------------------------
 kern - 08-04-2005 15:05 PDT 
----------------------------------------------------------------------
Thank you for figuring out the basic problem and providing all the
necessary information.

The problem is that you have given your File daemon and your Storage
daemon the same name, so some of the temporary file names collide.  IMO,
this is not a bug, but perhaps it could be better documented. Aside from
the name collisions, by using the same name rather than xxx-fd and xxx-sd
as recommended, it is impossible to know what daemon generates error
messages.

Give your daemons unique names and the problem will go away (hopefully).

I'll improve the documentation to warn about this.

Bug History
Date Modified  Username       Field                    Change              
======================================================================
08-04-05 10:22 ttoomey        New Bug                                      
08-04-05 15:05 kern           Bugnote Added: 0001104                       
08-04-05 15:05 kern           Resolution               open => not a bug   
08-04-05 15:05 kern           Status                   new => closed       
======================================================================