Re: [Bacula-users] Record header index xxxx not equal record index yyyy

2013-11-13 Thread Kern Sibbald
Hello, You might want to check your kernel logs to see if you have had any recent disk errors. The code that does bextract is identical to the code that reads and sends files to the FD, so it sounds to me more like a hard disk error. Best regards, Kern On 11/12/2013 10:27 AM, Christoph Litauer

Re: [Bacula-users] Record header index xxxx not equal record index yyyy

2013-11-12 Thread Christoph Litauer
Kern, thank you for your quick response. I did the restore twice with exactly the same numbers in the error message. As the autochanger is a disk based changer, the "drives" are virtual (symbolic links) so I won't expect any difference. I tried to read the tapes using bscan, but it crashes with

Re: [Bacula-users] Record header index xxxx not equal record index yyyy

2013-11-11 Thread Kern Sibbald
I am assuming that aleph1 is the name of your File daemon, and what it is say is that it had received a header for the 309262 record, and when the record arrived it was 329209, so it gave up. The errors after that one are meaningless ... This may have been a one time comm line hit or error, or it