Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I posted some time ago about the fill command failing giving me this type
Error: Re-read last block at EOT failed. ERR=block.c:1029 Read zero bytes
at 568:0 on device "LTO5" (/dev/nst0).
Some suggested it might be related to hardware compression so I since
had a chance to disable it (library in production) and test without
and unfortunatelly the problem remains.
Restores work. However, someone at work told me he had a similar
problem once and disregarded the messages.
But after his drive died, the replacement one couldn't reread the
tapes due to the error and he needed to find the same series of drive
as the broken one.
This is extremely scary regarding the importance of these archives.
Someone suggested in my last mail that it was OK but did not explain why.
Could anybody explain ?
I'm using a DELL TL2000 with
bacula Version: 5.0.2 (28 April 2010) x86_64-pc-linux-gnu debian squeeze/sid
Thanks in advance for any help,