Stefan Muenkner writes:
> Hi,
>
> maybe this is too obvious, but AFAIK the fd-client version should not be
> higher (it can be lower...) than the dir version. If, what you wrote was
> correct (dir 3.0.2 and fd 5.0.2) could that be causing problems ?
>
This could be and I'm going to investiga
Tobias Brink writes:
> So I still don't know how to proceed. Apart from that I will try to
> upgrade my director and sd to 5.0.2 as soon as Debian backports are
> available and see if the problem goes away. I will also re-run the
> DiskToCatalog after my next differential backup and see if some
On 08/30/2010 06:35 PM, Tobias Brink wrote:
> Steve Costaras writes:
>
>> Could be due to a transient error (transmission or wild/torn read at
>> time of calculation). I see this a lot with integrity checking of
>> files here (50TiB of storage).
>>
>> Only way to get around this now is to do a
'Paul Mather' wrote:
>On Aug 30, 2010, at 6:41 AM, Henrik Johansen wrote:
>
>> Like most ZFS related stuff it all sounds (and looks) extremely easy but
>> in reality it is not quite so simple.
>
>Yes, but does ZFS makes things easier or harder?
It hides a lot of the complexity involved. In ZFS it
Steve Costaras writes:
> Could be due to a transient error (transmission or wild/torn read at
> time of calculation). I see this a lot with integrity checking of
> files here (50TiB of storage).
>
> Only way to get around this now is to do a known-good sha1/md5 hash of
> data (2-3 reads of the
On Aug 30, 2010, at 6:41 AM, Henrik Johansen wrote:
> Like most ZFS related stuff it all sounds (and looks) extremely easy but
> in reality it is not quite so simple.
Yes, but does ZFS makes things easier or harder?
Silent data corruption won't go away just because your pool is large. :-)
(But,
'Steve Costaras' wrote:
> A little mis-quoted there:
>
>On 2010-08-30 02:59, Henrik Johansen wrote:
>>> On Aug 28, 2010, at 7:12 AM, Steve Costaras wrote:
>>>
>>> Could be due to a transient error (transmission or wild/torn read at
>>> time of calculation). I see this a lot with integrity checkin
A little mis-quoted there:
On 2010-08-30 02:59, Henrik Johansen wrote:
>> On Aug 28, 2010, at 7:12 AM, Steve Costaras wrote:
>>
>> Could be due to a transient error (transmission or wild/torn read at
>> time of calculation). I see this a lot with integrity checking of
>> files here (50TiB of st
'Paul Mather' wrote:
>On Aug 28, 2010, at 7:12 AM, Steve Costaras wrote:
>
>Could be due to a transient error (transmission or wild/torn read at
>time of calculation). I see this a lot with integrity checking of
>files here (50TiB of storage).
>
>Only way to get around this now is to do a known-go
On 8/28/2010 3:54 PM, Steve Costaras wrote:
> True, ZFS does offer some benefit here, though with oracle dropping
> opensolaris completely that means you are stuck with solaris x86 or
> solaris sparc.
If you want ZFS, there are more choices than that. Personally, my OS of
choice is FreeBSD. Z
True, ZFS does offer some benefit here, though with oracle dropping
opensolaris completely that means you are stuck with solaris x86 or
solaris sparc.BTRFS is a ways away for any real solution for
production use (years to reach the same level of debugging as zfs).
The point on large dr
On Aug 28, 2010, at 7:12 AM, Steve Costaras wrote:
> Could be due to a transient error (transmission or wild/torn read at time of
> calculation). I see this a lot with integrity checking of files here (50TiB
> of storage).
>
> Only way to get around this now is to do a known-good sha1/md5 has
Could be due to a transient error (transmission or wild/torn read at
time of calculation). I see this a lot with integrity checking of
files here (50TiB of storage).
Only way to get around this now is to do a known-good sha1/md5 hash of
data (2-3 reads of the file make sure that they all ma
Hello!
I run Bacula 3.0.2 (dir and sd) from Debian backports and bacula-fd
5.0.2 (Debian testing) on the client and I have a problem with a disk to
catalog verify job.
I make differential backups every week which get consolidated into a
full backup with the VirtualFull feature once a month. Now
14 matches
Mail list logo
