Re: [Bacula-users] Volume Error

2007-12-11 Thread Michael Galloway
here is what was in the log file: Dec 10 09:34:04 molbio kernel: st0: Current: sense key: Medium Error Dec 10 09:34:04 molbio kernel: Additional sense: Recorded entity not found Dec 10 09:34:04 molbio kernel: Info fld=0x1 i've marked it as used, and will see what happens. if it errors out aga

Re: [Bacula-users] Volume Error

2007-12-11 Thread Arno Lehmann
Hi, 11.12.2007 22:06,, Michael Galloway wrote:: > thanks for helping arno, here is what i've found: > > On Tue, Dec 11, 2007 at 09:36:06PM +0100, Arno Lehmann wrote: >> First of all, it's quite important to know why it's been marked as >> "Error". You can look that up in the log file Bacula, by

Re: [Bacula-users] Volume Error

2007-12-11 Thread Michael Galloway
also, i should have noted, this is bacula 2.2.6 with these patches: 2.2.6-add.patch 2.2.6-backup-restore-socket.patch 2.2.6-queued-msg.patch 2.2.6-status.patch running on centos 5. -- michael - SF.Net email is sponsored b

Re: [Bacula-users] Volume Error

2007-12-11 Thread Michael Galloway
thanks for helping arno, here is what i've found: On Tue, Dec 11, 2007 at 09:36:06PM +0100, Arno Lehmann wrote: > > First of all, it's quite important to know why it's been marked as > "Error". You can look that up in the log file Bacula, by default, > writes. A grep for the volume name should

Re: [Bacula-users] Volume Error

2007-12-11 Thread Arno Lehmann
Hi, 11.12.2007 19:29,, Michael Galloway wrote:: > ok, i don't really know what to do with this volume that is marked > as error. First of all, it's quite important to know why it's been marked as "Error". You can look that up in the log file Bacula, by default, writes. A grep for the volume nam