Hello,
Thanks for the feedback. Very good idea to run the memory tests. I
should have thought of that myself.
It is nice to know that you have resolved the problem. Fortunately
Bacula checksums the blocks :-)
Best regards,
Kern
On 07/04/2014 05:03 PM, advan...@posteo.de wrote:
> On Sat, 28 J
On Sat, 28 Jun 2014 09:30:12 +0200
Kern Sibbald wrote:
> It is unlikely that this is a Bacula problem, especially considering
> your remark that you have
> used it for years and never had any problems.
Hi List,
first of all I have to say thanks for all the helpful replies.
I checked every disk
On 06/30/2014 10:35 PM, John Stoffel wrote:
> Kern> Yes, it is clear that one can do read-only tests that do not destroy
> Kern> data. However, in this case, it seems to me more useful to do
> Kern> read/write (it is actually write/read) tests as it appears that the
> Kern> problem is more likely
Kern> Yes, it is clear that one can do read-only tests that do not destroy
Kern> data. However, in this case, it seems to me more useful to do
Kern> read/write (it is actually write/read) tests as it appears that the
Kern> problem is more likely in the write ...
Absolutely. And hopefully, this
I have seen this before with both disk and tape media, where a backup
job with no errors cannot later be restored due to i/o errors. The
simple answer is that media can fail, even when offline, which is one of
the reasons we make more than one backup.
It is possible, if cumbersome and expensive
Hello,
Yes, it is clear that one can do read-only tests that do not destroy
data. However, in this case, it seems to me more useful to do
read/write (it is actually write/read) tests as it appears that the
problem is more likely in the write ...
I have never heard of a non-destructive read/writ
Kern> 3. Run read/write disk tests on your USB disk (note: this will
Kern> destroy any existing data).
This isn't quite right. You can run read-write tests on a quiescent
filesystem (ie unmounted) without problems:
badblocks -svn /dev/sd?
will scan the entire disk using non-destructive read
It is unlikely that this is a Bacula problem, especially considering
your remark that you have
used it for years and never had any problems.
My best guess is that you have bad media or a bad medium or a bad
connector. When writing, unless the OS reports an error, Bacula assumes
the write is good.
Hi Liste,
I am using Bacula for years now and had no trouble so far.
But now it really hits me.
Well it worked smoothly .. until restore. (on ubuntu 12LTS and ubuntu
14, bacula version 5.2.6)
The files were on USB disk. To be on the safe side I recreated
everything on local sata again. Same res
