Hello,
my problem seems to be solved. It seems to have something to do with the block
size. I set both the minimum and the maximum blocksize of the device to 64KB
and the restore works:
Device {
Name = TestStorage
Media Type = File
Archive Device = /mnt/notfallserver/vollbackup
Hello Kern,
thank you very much for this hint, but the volume size is already limited to
2GB.
Greetings
Sven Hendriks
Von: Kern Sibbald [EMAIL PROTECTED]
Gesendet: 26.02.07 19:37:24
An: bacula-users@lists.sourceforge.net
Betreff: Re: [Bacula-users] Bacula Restore keeps crashing with Block
2,000,000,000
when it gets the error.
Greetings
Sven Hendriks
Von: Kern Sibbald [EMAIL PROTECTED]
Gesendet: 26.02.07 19:37:24
An: bacula-users@lists.sourceforge.net
Betreff: Re: [Bacula-users] Bacula Restore keeps crashing with Block
checksum mismatch
It looks to me like Samba
On Mon, 26 Feb 2007, Kern Sibbald wrote:
It looks to me like Samba shares don't support more that 2GB.
Incorrect. My CIFS servers are happily providing 1000+Gb shares.
It's certainly suboptimal for Bacula to be reading or writing to remote
shares though. Far better to put a samba-fd directly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kern Sibbald wrote:
On Tuesday 27 February 2007 09:54, Sven Hendriks wrote:
Hello Kern,
thank you very much for this hint, but the volume size is already limited
to 2GB.
Well, I don't think it is working correctly, because your output
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Brown wrote:
On Mon, 26 Feb 2007, Kern Sibbald wrote:
It looks to me like Samba shares don't support more that 2GB.
Incorrect. My CIFS servers are happily providing 1000+Gb shares.
It's certainly suboptimal for Bacula to be reading or
Hello,
I'm running Bacula 2.0.2 built from source on the following system:
XEN 3.0 with Gentoo, Kernel 2.6.16 as Dom0 running bacula-dir and bacula-sd.
One deamon bacula-fd is also running here for test restores. File system is
Ext3.
Debian, Kernel 2.6.16 as DomU running one file daemon for
It looks to me like Samba shares don't support more that 2GB.
Recommendations:
- Don't write to any share of any kind (not Samba, not NFS, ...)
- If you absolutely must write to a Samba share try limiting the Volume size
to 2GB -- that may resolve the problem.
On Monday 26 February 2007 09:50,
