Re: [Bacula-users] files larger 2 GByte on Windows 2003 Server?

[Kern S. <ke...@si...>]

Hello,

On Mon, 2003-11-17 at 14:36, Stephan Ebelt wrote:
> Kern Sibbald wrote:
> > Hello,
> > 
> > I suspect that the problem is an editing problem in the Director.  On
> > what OS and version are you running the Director?
> > 
> > Save a copy of your src/dird/backup.c file because it will be modified
> > by the patch, and you probably will not want to keep the patch (it does
> > no harm).
> > 
> > Please apply the patch that is attached, then rerun your backup with a
> > file greater than 2Gb.  Keep the window in which you launch the Director
> > open, and one line of debug information should print when the job is
> > done.  Patch instructions are in the top of the attachment file.
> 
> Hello,
> 
> sorry for late reply - a wisdom tooth detained me from working last week...

Sorry, I also had some health problems so I also a week late ...

The patch tells me that the problem is coming on the Windows side. After
thinking about this a bit more, I am *almost* convinced that it is a
simple editing problem and that Bacula is actually backing up your file
correctly (as can be seen from the SD reports).

I suggest that you try restoring the file and see if you get back little
measly 288 bytes or you get back the full file.

It seems to me that Cygwin have fixed the 2G limit in their stat()
packet in version 1.5.5, which is what I am now using for 1.33.  The
problem is that I'm not 100% sure that I set the right things to get
them to turn on 64 bit file addresses.  I'm going to take a look at that
so that I can get the statistics correctly corresponding to what was
actually saved.

Best regards,

Kern

> 
> Anyway, thank you for the patch and (of course) the great work on 
> bacula. It's working very fine for me. Except the problem with this 
> Windows machine. Right now are 10 Servers holding ~500 GByte in about 
> 1.5 million files backed up daily.
> 
> The director and storage daemons are running on RedHat 9 and it is both 
> 1.32d. The file daemon is on M$ Windows 2003 Server.
> 
> The patch now shows this debug information:
> 
> ebest.dd.net-linx: backup.c:241 2800 End Job TermCode=84 JobFiles=3 
> ReadBytes=288 JobBytes=288 Errors=0
> 
> The status message printed on the console is still as mentioned in the 
> last e-mail.
> 
> (to avoid confusion about the host names: I used another director 
> machine to run this test. Since I wouldn't like to play around with my 
> production installation.
> However, the OS and Bacula versions are the same and of course the 
> client is the same machine. Also I monitor the same behavior on my test 
> director.
> So it should be OK to use the test machine to find out what's going wrong.)
> 
> best regards,
> Stephan
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF. Net email is sponsored by: GoToMyPC
> GoToMyPC is the fast, easy and secure way to access your computer from
> any Web browser or wireless device. Click here to Try it Free!
> https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
> _______________________________________________
> Bacula-users mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/bacula-users