[Bacula-users] Re: Backup Problem: The number of files mismatch!

2006-01-19 Thread Lance Brown
Arno Lehmann wrote: > That said, the question is "Why does the SD need 4 minutes to find that > there are no file marks on tape?" > > I don't know the answer. > > BUT I'd suggest that you do the following: > - Check the system log for any tape or SCSI related errors. Use tapeinfo > to see the tap

[Bacula-users] Re: Backup Problem: The number of files mismatch!

2006-01-19 Thread Lance Brown
Kern Sibbald wrote: > Below are a few guesses. They are a large part guesses because you didn't > specify enough information: please see the Support page on the web site. My mistake. System Information: Server:Dell PowerEdge 2650 OS:CentOS 3.6 (fully updated) SCSI Card: LSI Logic /

[Bacula-users] Backup Problem: The number of files mismatch!

2006-01-19 Thread Lance Brown
I got this message in my logs from the backup run last night: 19-Jan 02:16 what-sd: Volume "Monthly-0004" previously written, moving to end of data. 19-Jan 02:22 what-sd: What.2006-01-19_02.05.01 Error: I canot write on Volume "Monthly-0004" because: The number of files mismatch! Volume=0 Catalog=

[Bacula-users] Re: LTO-3 vs. fixed block sizes

2006-01-17 Thread Lance Brown
Lance Brown wrote: > btape from 1.38.4 succeeds with my tape library on a freshly installed > CentOS 4 system. I had to swipe the SCSI card from my current CentOS 3 > backup server in order to test it so I'm not 100% sure it's C4 vs. C3, > or just that a loose connection got

[Bacula-users] Re: LTO-3 vs. fixed block sizes

2006-01-17 Thread Lance Brown
Lance Brown wrote: > Lance Brown wrote: > >>I used the terminator that came with the new library, but I don't recall >>switching it out for my old one. I'll give that a try. > > > *grrr* No change in behaviour. Programs still hang on the last read() >

[Bacula-users] Re: LTO-3 vs. fixed block sizes

2006-01-17 Thread Lance Brown
Lance Brown wrote: > I used the terminator that came with the new library, but I don't recall > switching it out for my old one. I'll give that a try. *grrr* No change in behaviour. Programs still hang on the last read() system call. Time to build a CentOS 4 box and see

[Bacula-users] Re: LTO-3 vs. fixed block sizes

2006-01-17 Thread Lance Brown
Alan Brown wrote: > As a really dumb (but non-obvious) question, have you tried swapping out > the terminator? I used the terminator that came with the new library, but I don't recall switching it out for my old one. I'll give that a try. --[Lance] -- Lance A. Brown Senior Systems Programmer I

[Bacula-users] Re: LTO-3 vs. fixed block sizes

2006-01-16 Thread Lance Brown
Rudolf Cejka wrote: > Hello, maybe you can try different version of Linux, newer Bacula 1.38.x > or/and cabling. I have Overland Neo 4200 with LTO-3 and FreeBSD 6.0 > and did not experience any problem like yours - and I think there are > others with LTO-3 without problems independently on FreeBSD

[Bacula-users] LTO-3 vs. fixed block sizes

2006-01-13 Thread Lance Brown
Greetings, I wrote a message titled 'Problem with LTO-3 drive' to the list a few days ago but received no reply to it. Since then I've discovered some new information. I have a new Exabyte Magnum 1x7 autoloader with an IBM LTO-3 drive and it appears I *have* to use fixed block sizes otherwise it