Josh Fisher wrote:
Brandon Evans wrote:
Arno Lehmann wrote:
I agree ,this is very strange. Here is what I am running
CentOS 4.1, Bacula 1.36.3 with kernel version 2.6.12.2
The /mnt/coraid partition which bacula backs up to is a ext3
partation ontop of LVM, and Raid 5
I could just add more volumes to the pool, but I was wanting this
setup so it would be eaiser to manage.
Given the available information, I'd look closely into your system
log and kenel messages - it might be problem with your filesystem or
hardware.
Arno
I do not see anything in the logs related to disk troubles. I am able
to write to the /mnt/coraid partation with no problems.
Just in case, I setup another device that stores the volumes on a
local disk. I'm running the job right now. I'll update this post
once it hits 17 Gigs
What happens when you remove the "Maximum Volume Bytes" line altogether?
I started out without a "Maximum Volume Bytes" setting when this issue
first started. That line was added because I thought it might be
necessary to go over 17Gigs.
After moving the Job to another device on another partition, the backup
was able tom complete. It looks like this is going to be a filesystem /
hardware related error.
Now comes the fun part of trying to figure out where exactly the problem is.
Thank you to all who helped.
--
Thanks,
Brandon Evans
"I wouldn't recommend sex, drugs or insanity for everyone, but they've
always worked for me."
-Hunter S. Thompson
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
