Re: [Bacula-users] ERR=Device or resource busy
Dear Kern, in message [EMAIL PROTECTED] you wrote: Thanks for the feedback. I'm happy to see that your problem is resolved. I start seeing this problem now, too, especially when running several jobs (with data spooling) in parallel, and when the tape gets full. I guess that the next time I respond, I should not only mention the fact that Bacula tends to expose a lot of driver bugs AND hardware problems, both of which are difficult and time consuming to debug ... I don't think it's either of these in my case. When I run into this situation, I can reliably reproduce the problem (but I don't know which exact conditions trigger it in the first place). Here is what happens: 17-Aug 00:40 nyx-sd: Spooling data ... 17-Aug 00:40 nyx-sd: Committing spooled data to Volume K-V-DAT-3. Despooling 1,985,286 bytes ... 17-Aug 00:40 nyx-sd: Source-Other.2006-08-17_00.10.04 Error: block.c:538 Write error at 22:2740 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. 17-Aug 00:40 nyx-sd: Re-read of last block succeeded. 17-Aug 00:40 nyx-sd: End of medium on Volume K-V-DAT-3 Bytes=15,118,094,426 Blocks=234,370 at 17-Aug-2006 00:40. 17-Aug 00:41 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 17-Aug 00:41 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 3. 17-Aug 00:41 nyx-sd: 3307 Issuing autochanger unload slot 3, drive 0 command. 17-Aug 00:42 nyx-sd: 3304 Issuing autochanger load slot 4, drive 0 command. 17-Aug 00:43 nyx-sd: 3305 Autochanger load slot 4, drive 0, status is OK. 17-Aug 00:43 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 17-Aug 00:43 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 4. 17-Aug 00:43 nyx-sd: Wrote label to prelabeled Volume K-V-DAT-4 on device DDS-3 (/dev/nst0) 17-Aug 00:43 nyx-sd: New volume K-V-DAT-4 mounted on device DDS-3 (/dev/nst0) at 17-Aug-2006 00:43. 17-Aug 00:43 nyx-sd: Source-Other.2006-08-17_00.10.04 Error: block.c:538 Write error at 0:1 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. 17-Aug 00:43 nyx-sd: Source-Other.2006-08-17_00.10.04 Error: Re-read of last block OK, but block numbers differ. Last block=0 Current block=0. 17-Aug 00:43 nyx-sd: Source-Other.2006-08-17_00.10.04 Fatal error: spool.c:249 Fatal append error on device DDS-3 (/dev/nst0): ERR=dev.c:678 Rewind error on DDS-3 (/dev/nst0). ERR=Input/output error. ... 18-Aug 00:40 nyx-sd: Committing spooled data to Volume K-V-DAT-4. Despooling 948,750,016 bytes ... 18-Aug 00:40 nyx-sd: Castor-Home-1.2006-08-18_00.05.00 Error: block.c:538 Write error at 2:6438 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. 18-Aug 00:41 nyx-sd: Re-read of last block succeeded. 18-Aug 00:41 nyx-sd: End of medium on Volume K-V-DAT-4 Bytes=691,688,327 Blocks=10,727 at 18-Aug-2006 00:41. 18-Aug 00:41 castor-dir: Recycled volume K-V-DAT-1 18-Aug 00:41 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 18-Aug 00:41 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 4. 18-Aug 00:41 nyx-sd: 3307 Issuing autochanger unload slot 4, drive 0 command. 18-Aug 00:41 nyx-sd: 3304 Issuing autochanger load slot 1, drive 0 command. 18-Aug 00:42 nyx-sd: 3305 Autochanger load slot 1, drive 0, status is OK. 18-Aug 00:42 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 18-Aug 00:42 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 1. 18-Aug 00:42 nyx-sd: Recycled volume K-V-DAT-1 on device DDS-3 (/dev/nst0), all previous data lost. 18-Aug 00:42 nyx-sd: New volume K-V-DAT-1 mounted on device DDS-3 (/dev/nst0) at 18-Aug-2006 00:42. 18-Aug 00:42 nyx-sd: Castor-Home-1.2006-08-18_00.05.00 Error: block.c:538 Write error at 0:1 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. 18-Aug 00:42 nyx-sd: Castor-Home-1.2006-08-18_00.05.00 Error: Re-read of last block OK, but block numbers differ. Last block=0 Current block=0. 18-Aug 00:42 nyx-sd: Castor-Home-1.2006-08-18_00.05.00 Fatal error: spool.c:249 Fatal append error on device DDS-3 (/dev/nst0): ERR=dev.c:678 Rewind error on DDS-3 (/dev/nst0). ERR=Input/output error. ... 18-Aug 00:42 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 18-Aug 00:42 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 1. 18-Aug 00:42 nyx-sd: Castor-Home-2.2006-08-18_00.10.00 Error: block.c:538 Write error at 0:0 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. 18-Aug 00:43 nyx-sd: Castor-Home-2.2006-08-18_00.10.00 Error: Backspace record at EOT failed. ERR=Input/output error 18-Aug 00:43 nyx-sd: Castor-Home-2.2006-08-18_00.10.00 Error: label.c:441 Unable to write device DDS-3 (/dev/nst0): ERR=dev.c:1430 ioctl MTBSR error on DDS-3 (/dev/nst0). ERR=Input/output error. 18-Aug 00:43 nyx-sd: Marking Volume K-V-DAT-1 in Error in Catalog. In this state, the newly mounted volumes (K-V-DAT-4 and K-V-DAT-1) are empty, i. e. they have NO data on it. Even the previously existing bacula labels are gone. I can now reproduce this failure mode; for example, I try to recycle the last
Re: [Bacula-users] ERR=Device or resource busy
Hello Wolfgang, As I have mentioned before, I believe that this is an OS bug. I have been able to reproduce it here, and I believe it happens when you send too much data too fast to the OS. Please see below for more comments: On Friday 18 August 2006 18:22, Wolfgang Denk wrote: Dear Kern, in message [EMAIL PROTECTED] you wrote: Thanks for the feedback. I'm happy to see that your problem is resolved. I start seeing this problem now, too, especially when running several jobs (with data spooling) in parallel, and when the tape gets full. I guess that the next time I respond, I should not only mention the fact that Bacula tends to expose a lot of driver bugs AND hardware problems, both of which are difficult and time consuming to debug ... I don't think it's either of these in my case. When I run into this situation, I can reliably reproduce the problem (but I don't know which exact conditions trigger it in the first place). Here is what happens: 17-Aug 00:40 nyx-sd: Spooling data ... 17-Aug 00:40 nyx-sd: Committing spooled data to Volume K-V-DAT-3. Despooling 1,985,286 bytes ... 17-Aug 00:40 nyx-sd: Source-Other.2006-08-17_00.10.04 Error: block.c:538 Write error at 22:2740 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. 17-Aug 00:40 nyx-sd: Re-read of last block succeeded. 17-Aug 00:40 nyx-sd: End of medium on Volume K-V-DAT-3 Bytes=15,118,094,426 Blocks=234,370 at 17-Aug-2006 00:40. 17-Aug 00:41 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 17-Aug 00:41 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 3. 17-Aug 00:41 nyx-sd: 3307 Issuing autochanger unload slot 3, drive 0 command. 17-Aug 00:42 nyx-sd: 3304 Issuing autochanger load slot 4, drive 0 command. 17-Aug 00:43 nyx-sd: 3305 Autochanger load slot 4, drive 0, status is OK. 17-Aug 00:43 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 17-Aug 00:43 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 4. 17-Aug 00:43 nyx-sd: Wrote label to prelabeled Volume K-V-DAT-4 on device DDS-3 (/dev/nst0) 17-Aug 00:43 nyx-sd: New volume K-V-DAT-4 mounted on device DDS-3 (/dev/nst0) at 17-Aug-2006 00:43. 17-Aug 00:43 nyx-sd: Source-Other.2006-08-17_00.10.04 Error: block.c:538 Write error at 0:1 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. The above error Device or resource should never happen, from what I know about Linux. The write() system call should be a blocking call and it should never return busy, thus I consider this is most likely an operating system bug. The proper behavior is for the OS to simply wait until the I/O is complete and then return. At one point, I was able to reproduce this problem here, and in 1.39.x I have what I consider a really crude workaround. Basically Bacula will retry the I/O after waiting a bit. Using this technique, I was able to eliminate the problem here, but I am not really satisfied with the fix as the amount of time that Bacula needs to wait is indeterminant. As far as I can tell, this problem occurs because Bacula is feeding data to the tape drive too fast. I can only guess that the OS memory is getting completely full and at some point rather than making Bacula wait as it should, the OS returns an error code. After that point, everything for that particular job is more or less screwed up as you can see in the output that follows, because Bacula gets an error during the rewind since the OS is probably still busy. 17-Aug 00:43 nyx-sd: Source-Other.2006-08-17_00.10.04 Error: Re-read of last block OK, but block numbers differ. Last block=0 Current block=0. 17-Aug 00:43 nyx-sd: Source-Other.2006-08-17_00.10.04 Fatal error: spool.c:249 Fatal append error on device DDS-3 (/dev/nst0): ERR=dev.c:678 Rewind error on DDS-3 (/dev/nst0). ERR=Input/output error. ... 18-Aug 00:40 nyx-sd: Committing spooled data to Volume K-V-DAT-4. Despooling 948,750,016 bytes ... 18-Aug 00:40 nyx-sd: Castor-Home-1.2006-08-18_00.05.00 Error: block.c:538 Write error at 2:6438 on device DDS-3 (/dev/nst0). ERR=Device or resource busy. 18-Aug 00:41 nyx-sd: Re-read of last block succeeded. 18-Aug 00:41 nyx-sd: End of medium on Volume K-V-DAT-4 Bytes=691,688,327 Blocks=10,727 at 18-Aug-2006 00:41. 18-Aug 00:41 castor-dir: Recycled volume K-V-DAT-1 18-Aug 00:41 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 18-Aug 00:41 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 4. 18-Aug 00:41 nyx-sd: 3307 Issuing autochanger unload slot 4, drive 0 command. 18-Aug 00:41 nyx-sd: 3304 Issuing autochanger load slot 1, drive 0 command. 18-Aug 00:42 nyx-sd: 3305 Autochanger load slot 1, drive 0, status is OK. 18-Aug 00:42 nyx-sd: 3301 Issuing autochanger loaded drive 0 command. 18-Aug 00:42 nyx-sd: 3302 Autochanger loaded drive 0, result is Slot 1. 18-Aug 00:42 nyx-sd: Recycled volume K-V-DAT-1 on device DDS-3 (/dev/nst0), all previous data lost. 18-Aug 00:42 nyx-sd: New volume
Re: [Bacula-users] ERR=Device or resource busy
On Mon, 5 Jun 2006, Kern Sibbald wrote: Unfortunately, Bacula is sufficiently demanding that it often brings out driver problems that don't show up using most Unix tape utilities, which tend to be rather simple minded. They either simply write() or read(). Bacula uses quite a lot more features of the drive. just in case anyone tracks down my original mail to the list, and wonders how i resolved it, i should point out i've fixed it. it seems that it was hardware. basically, something on my old system was going south. i suspect it was the processor, as it was so hard to track down, but i shotgunned the entire system (except for the HDD, which i had no reason to suspect, the PSU, which had only just been replaced in an earlier attempt to solve the problem, and the SCSI card, which i can't afford to replace and which i have some confidence in) and put in new motherboard, memory, processor, fan, video card and case. the new system came up and immediately started running bacula just fine. enormous thanks to kern for responding quickly, informatively and personally. -- Tom Yates - [EMAIL PROTECTED] - http://www.teaparty.net Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ERR=Device or resource busy
On Wednesday 28 June 2006 12:13, Tom Yates wrote: On Mon, 5 Jun 2006, Kern Sibbald wrote: Unfortunately, Bacula is sufficiently demanding that it often brings out driver problems that don't show up using most Unix tape utilities, which tend to be rather simple minded. They either simply write() or read(). Bacula uses quite a lot more features of the drive. just in case anyone tracks down my original mail to the list, and wonders how i resolved it, i should point out i've fixed it. it seems that it was hardware. basically, something on my old system was going south. i suspect it was the processor, as it was so hard to track down, but i shotgunned the entire system (except for the HDD, which i had no reason to suspect, the PSU, which had only just been replaced in an earlier attempt to solve the problem, and the SCSI card, which i can't afford to replace and which i have some confidence in) and put in new motherboard, memory, processor, fan, video card and case. the new system came up and immediately started running bacula just fine. enormous thanks to kern for responding quickly, informatively and personally. Thanks for the feedback. I'm happy to see that your problem is resolved. I guess that the next time I respond, I should not only mention the fact that Bacula tends to expose a lot of driver bugs AND hardware problems, both of which are difficult and time consuming to debug ... -- Best regards, Kern ( /\ V_V Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ERR=Device or resource busy
Kern Sibbald wrote: Unfortunately, Bacula is sufficiently demanding that it often brings out driver problems that don't show up using most Unix tape utilities, which tend to be rather simple minded. They either simply write() or read(). Bacula uses quite a lot more features of the drive. That's very interesting. I've lost a certain degree of faith in the SCSI card I'm using; it's not particularly common so there's every possibility the driver hasn't had as much exercise as some of the more common SCSI card drivers. I'm wondering if it's worth replacing the SCSI card with something a little more commonplace - I'm thinking a reasonably sensible Adaptec card right now, maybe using the aic7xxx driver - has anyone had any experience of these? ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ERR=Device or resource busy
On Tuesday 06 June 2006 10:04, James Cort wrote: Kern Sibbald wrote: Unfortunately, Bacula is sufficiently demanding that it often brings out driver problems that don't show up using most Unix tape utilities, which tend to be rather simple minded. They either simply write() or read(). Bacula uses quite a lot more features of the drive. That's very interesting. I've lost a certain degree of faith in the SCSI card I'm using; it's not particularly common so there's every possibility the driver hasn't had as much exercise as some of the more common SCSI card drivers. I'm wondering if it's worth replacing the SCSI card with something a little more commonplace - I'm thinking a reasonably sensible Adaptec card right now, maybe using the aic7xxx driver - has anyone had any experience of these? I always use Adaptec cards from the beginning of the Bacula project and the aic7xxx driver and have had very few problems. The kernel bug lists have frequently reported all kinds of horrible problems with scsi drivers (including aic7xxx), but fortunately in the last 6 years, I only had one kernel that had a really broken scsi driver. IMO, if you are using a non-standard scsi card, your chance of problems at some point goes up rather astronomically judging from the kernel bug reports and user reports I have seen (not at alll a scientific study ...). -- Best regards, Kern ( /\ V_V ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] ERR=Device or resource busy
On Fri, 2 Jun 2006, Kern Sibbald wrote: This could be a problem with tapes, but the error message Device or resource busy not a normal error message for tape error. It looks more like some sort of driver problem (OS/Kernel driver, tape drive firmware, SCSI controller, or Bacula). i've been consistently getting those with every single bacula operation on my FC5 box (running the storage director) since i upgraded the kernel from kernel-2.6.16-1.2111_FC5 to kernel-2.6.16-1.2122_FC5 (specifically, i keep getting ERR=block.c:945 Read error at file:blk 0:0 on device Drive0 (/dev/nst0). ERR=Device or resource busy. i confess that i haven't rebooted with the old kernel to check things still work, but upgrading from bacula 1.38.8 to 1.38.9 (on the sd box) hasn't helped. mtx-changer still works, and when bacula's stopped i can still dd data off the tape. can anyone shed any light on why this might be happening? -- Tom Yates Cambridge, UK. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ERR=Device or resource busy
On Mon, 5 Jun 2006, Kern Sibbald wrote: I'm running on kernel-2.6.16-1.2122_FC5 and not seeing the problems you are. However, I have only been running that system several days. I recommend the following things (obviously 2-4 are unnecessary if 1 fixes the problem): 1. This still looks most like a kernel driver problem to me. Backing up to kernel-2.6.16-1.2111 would most likely clear up this point. i'll try that as soon as i can clear time for a reboot, and will let the list know if that fixes it. knowing that you're running .2122 makes me a bit less worried (i feared some major API change that broke bacula across the board, instead of a just a driver issue with my SCSI card) - but i don't want to be at .2111 forever. if i could produce some kind of error that didn't involve bacula, i could log it with redhat's bugzilla, and try to make progress on that front. 2. Rebuild and reinstall Bacula (in case there are some library changes). done that, both for 1.38.8 (make distclean; ./configure) and 1.38.9 (built from freshly unpacked tarball) - for that very reason. 3. Clean your tape drive. good idea, i'll try it - but that way i can use dd to read and write to and from a blank tape (and, oddly, label it under 1.38.9 - but not then inventory it with an 'update slots=1 scan') makes me disinclined to suspect dirty tape heads. is that wrong reasoning? 4. Mark the current Volume as Used and try a different one. tried. six tapes - three full, one part-full, two blank - *all* fail to read in an 'update slots scan', with the same error. thanks for such a prompt, useful response with so much to try in it. news as it's made. -- Tom Yates - http://www.teaparty.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ERR=Device or resource busy
On Monday 05 June 2006 09:13, Tom Yates wrote: On Fri, 2 Jun 2006, Kern Sibbald wrote: This could be a problem with tapes, but the error message Device or resource busy not a normal error message for tape error. It looks more like some sort of driver problem (OS/Kernel driver, tape drive firmware, SCSI controller, or Bacula). i've been consistently getting those with every single bacula operation on my FC5 box (running the storage director) since i upgraded the kernel from kernel-2.6.16-1.2111_FC5 to kernel-2.6.16-1.2122_FC5 (specifically, i keep getting ERR=block.c:945 Read error at file:blk 0:0 on device Drive0 (/dev/nst0). ERR=Device or resource busy. i confess that i haven't rebooted with the old kernel to check things still work, but upgrading from bacula 1.38.8 to 1.38.9 (on the sd box) hasn't helped. mtx-changer still works, and when bacula's stopped i can still dd data off the tape. can anyone shed any light on why this might be happening? I'm running on kernel-2.6.16-1.2122_FC5 and not seeing the problems you are. However, I have only been running that system several days. I recommend the following things (obviously 2-4 are unnecessary if 1 fixes the problem): 1. This still looks most like a kernel driver problem to me. Backing up to kernel-2.6.16-1.2111 would most likely clear up this point. 2. Rebuild and reinstall Bacula (in case there are some library changes). 3. Clean your tape drive. 4. Mark the current Volume as Used and try a different one. -- Best regards, Kern ( /\ V_V ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ERR=Device or resource busy
Kern Sibbald wrote: I recommend the following things (obviously 2-4 are unnecessary if 1 fixes the problem): 1. This still looks most like a kernel driver problem to me. Backing up to kernel-2.6.16-1.2111 would most likely clear up this point. I've had a few kernel driver problems with this system in particular: 1. One day a few months ago, for no apparent reason, none of the kernels on the box would talk to the SCSI controller - even though it had been working fine for ages before then. An upgrade to a newer kernel fixed the issue. 2. This box hasn't been rebooted lately - and is therefore still using that known-good kernel (2.6.16.1 vanilla). Was fine until the last few days. Are there any known issues with LSI Logic SCSI cards? The thing I do notice is that this always happens around 130-150 GB into the tape: +-++---+-+--+--+-+--+---+---+-+ | mediaid | volumename | volstatus | volbytes| volfiles | volretention | recycle | slot | inchanger | mediatype | lastwritten | +-++---+-+--+--+-+--+---+---+-+ | 33 | 28 | Full | 148,190,480,717 | 148 | 2,332,800 | 1 |0 | 1 | Tape | 2006-06-05 14:15:35 | It's a Quantum DLTv4 drive which is only physically capable of writing to 160/320GB tapes so there's no earthly way it's filled up that tape. Most of the tapes it hasn't liked have thus far been recycled tapes which were previously written at 80/160GB, but have since been passed through a bulk eraser. 2. Rebuild and reinstall Bacula (in case there are some library changes). Haven't put anything new on there lately regarding Bacula. 3. Clean your tape drive. It's about 6 weeks old. 4. Mark the current Volume as Used and try a different one. Done that with 4 volumes now. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ERR=Device or resource busy
On Monday 05 June 2006 11:33, Tom Yates wrote: On Mon, 5 Jun 2006, Kern Sibbald wrote: I'm running on kernel-2.6.16-1.2122_FC5 and not seeing the problems you are. However, I have only been running that system several days. I recommend the following things (obviously 2-4 are unnecessary if 1 fixes the problem): 1. This still looks most like a kernel driver problem to me. Backing up to kernel-2.6.16-1.2111 would most likely clear up this point. i'll try that as soon as i can clear time for a reboot, and will let the list know if that fixes it. knowing that you're running .2122 makes me a bit less worried (i feared some major API change that broke bacula across the board, instead of a just a driver issue with my SCSI card) - but i don't want to be at .2111 forever. if i could produce some kind of error that didn't involve bacula, i could log it with redhat's bugzilla, and try to make progress on that front. Unfortunately, Bacula is sufficiently demanding that it often brings out driver problems that don't show up using most Unix tape utilities, which tend to be rather simple minded. They either simply write() or read(). Bacula uses quite a lot more features of the drive. 2. Rebuild and reinstall Bacula (in case there are some library changes). done that, both for 1.38.8 (make distclean; ./configure) and 1.38.9 (built from freshly unpacked tarball) - for that very reason. 3. Clean your tape drive. good idea, i'll try it - but that way i can use dd to read and write to and from a blank tape (and, oddly, label it under 1.38.9 - but not then inventory it with an 'update slots=1 scan') makes me disinclined to suspect dirty tape heads. is that wrong reasoning? 4. Mark the current Volume as Used and try a different one. tried. six tapes - three full, one part-full, two blank - *all* fail to read in an 'update slots scan', with the same error. thanks for such a prompt, useful response with so much to try in it. news as it's made. -- Best regards, Kern ( /\ V_V ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] ERR=Device or resource busy
Hi all!
i have a tape library attache:
# cat /proc/scsi/sg/device_strs
HP C1557A U812
HP C1557A U812
i can tar on the tape the changer works fine.
In /etc/bacula/bacula-dir.conf i have this storage and pool definitions
Storage {
Name = PorCheloStorage
Address = 192.168.1.40
SDPort = 9103
Password = karkoma
Device = PorCheloDevice
Autochanger =yes
Media Type = DDS-4
}
Pool {
Name = PorCheloPool
Pool Type = Backup
AutoPrune = yes
# Use Volume Once = yes
Recycle = yes
Volume Retention = 7 days
Maximum Volume Jobs = 1
Maximum Volumes = 7
Accept Any Volume = no
}
and in /etc/bacula/bacula-sd.conf i have this device definition
Device {
Name = PorCheloDevice
Media Type = DDS-4
Archive Device = /dev/st0# Normal archive device
Changer Device = /dev/sg0 # Generic SCSI device name
Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
Autochanger = yes
LabelMedia = no;
AutomaticMount = yes;
AlwaysOpen = yes;
# Mount Anonymous Volumes = no;
}
but if i try to label on this storage i become
3301 Issuing autochanger loaded drive 0 command.
3302 Autochanger loaded drive 0, result is Slot 1.
3910 Unable to open device /dev/st0. ERR=dev.c:289 stored: unable to
open device /dev/st0: ERR=Device or resource busy
Label command failed for Volume CENSALES.
Do not forget to mount the drive!!!
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] ERR=Device or resource busy
Hi all!
i have a tape library attache:
# cat /proc/scsi/sg/device_strs
HP C1557A U812
HP C1557A U812
i can tar on the tape the changer works fine.
In /etc/bacula/bacula-dir.conf i have this storage and pool definitions
Storage {
Name = PorCheloStorage
Address = 192.168.1.40
SDPort = 9103
Password = karkoma
Device = PorCheloDevice
Autochanger =yes
Media Type = DDS-4
}
Pool {
Name = PorCheloPool
Pool Type = Backup
AutoPrune = yes
# Use Volume Once = yes
Recycle = yes
Volume Retention = 7 days
Maximum Volume Jobs = 1
Maximum Volumes = 7
Accept Any Volume = no
}
and in /etc/bacula/bacula-sd.conf i have this device definition
Device {
Name = PorCheloDevice
Media Type = DDS-4
Archive Device = /dev/st0# Normal archive device
Changer Device = /dev/sg0 # Generic SCSI device name
Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
Autochanger = yes
LabelMedia = no;
AutomaticMount = yes;
AlwaysOpen = yes;
# Mount Anonymous Volumes = no;
}
but if i try to label on this storage (i have try with and whithout imt
-f /dev/st0 rewind and weof)i become:
3301 Issuing autochanger loaded drive 0 command.
3302 Autochanger loaded drive 0, result is Slot 1.
3910 Unable to open device /dev/st0. ERR=dev.c:289 stored: unable to
open device /dev/st0: ERR=Device or resource busy
Label command failed for Volume CENSALES.
Do not forget to mount the drive!!!
any idea what i made wrong? :-[
pascal
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
