Bug#337376: bacula-sd: No jobs possible with kernel 2.6 if no tape is in drive
On Friday 04 November 2005 13:05, José Luis Tallón wrote: > Christoph Haas wrote: >> So the package seems to be unusable by everyone who uses tapes for >> backups, runs a 2.6 Linux kernel and has no tape inserted in the drive >> when the backup starts. Of course I would love to see a fix for this >> problem even in Sarge if possible. Perhaps upstream can deliver a >> patch for the 1.36.2 version? > > It would be nice, but i'm not positive that it really is feasible... why > don't you ask? who knows, it might work > (if it is indeed produced, i would prepare an 'stable update' including > it) That's what the upstream said to my question on the mailing list: = If someone is very clever, perhaps one could patch it, otherwise, there is a *really* big difference between the 1.36.x code and the 1.38.0 that deals with this problem. = So it's probably not possible/easy. But perhaps you can add a note in the README.Debian? Christoph
Bug#337376: bacula-sd: No jobs possible with kernel 2.6 if no tape is in drive
Christoph Haas wrote: >Package: bacula-sd >Version: 1.36.2-2sarge1 >Severity: important > >Backup jobs are failing when using my DDS-3 streamer when there is no tape >inserted at the beginning of the backup. The job is instantly cancelled >with these error messages: > >== >03-Nov 08:11 torf-dir: Start Backup JobId 206, >Job=BackupCatalog.2005-11-03_08.10.00 > >03-Nov 08:13 torf-sd: BackupCatalog.2005-11-03_08.10.00 Fatal error: >device.c:317 Unable to open device /dev/nst0. ERR=dev.c:289 stored: unable >to open device /dev/nst0: ERR=Input/output error > >03-Nov 08:13 torf-fd: BackupCatalog.2005-11-03_08.10.00 Fatal error: >job.c:1665 Bad response to Append Data command. Wanted 3000 OK data >, got 3903 Error append data > >03-Nov 08:13 torf-dir: BackupCatalog.2005-11-03_08.10.00 Error: Bacula >1.36.2 (28Feb05): 03-Nov-2005 08:13:26 >== > >Kern Sibbald - the upstream developer - wrote on the mailing list: > >== >It looks like you stumbled into a change they made in the 2.6 kernel, which >will undoubtely cause a lot of people a *lot* of pain. The change prohibits >a program from opening a drive in read/write mode if there is no volume in >the drive. > >If this is what is causing your problem, you can solve it by: >1. Ensuring that there is some tape in the drive befort starting the SD, >and before issuing a "mount" command in the console. >2. Upgrade to version 1.38.0 (you might wait for a Win32 fix if you have >Win32 clients). >== > >So the package seems to be unusable by everyone who uses tapes for backups, >runs a 2.6 Linux kernel and has no tape inserted in the drive when the >backup starts. Of course I would love to see a fix for this problem even in >Sarge if possible. Perhaps upstream can deliver a patch for the 1.36.2 >version? > > It would be nice, but i'm not positive that it really is feasible... why don't you ask? who knows, it might work (if it is indeed produced, i would prepare an 'stable update' including it) Thank you. Best, J.L. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337376: bacula-sd: No jobs possible with kernel 2.6 if no tape is in drive
Package: bacula-sd Version: 1.36.2-2sarge1 Severity: important Backup jobs are failing when using my DDS-3 streamer when there is no tape inserted at the beginning of the backup. The job is instantly cancelled with these error messages: == 03-Nov 08:11 torf-dir: Start Backup JobId 206, Job=BackupCatalog.2005-11-03_08.10.00 03-Nov 08:13 torf-sd: BackupCatalog.2005-11-03_08.10.00 Fatal error: device.c:317 Unable to open device /dev/nst0. ERR=dev.c:289 stored: unable to open device /dev/nst0: ERR=Input/output error 03-Nov 08:13 torf-fd: BackupCatalog.2005-11-03_08.10.00 Fatal error: job.c:1665 Bad response to Append Data command. Wanted 3000 OK data , got 3903 Error append data 03-Nov 08:13 torf-dir: BackupCatalog.2005-11-03_08.10.00 Error: Bacula 1.36.2 (28Feb05): 03-Nov-2005 08:13:26 == Kern Sibbald - the upstream developer - wrote on the mailing list: == It looks like you stumbled into a change they made in the 2.6 kernel, which will undoubtely cause a lot of people a *lot* of pain. The change prohibits a program from opening a drive in read/write mode if there is no volume in the drive. If this is what is causing your problem, you can solve it by: 1. Ensuring that there is some tape in the drive befort starting the SD, and before issuing a "mount" command in the console. 2. Upgrade to version 1.38.0 (you might wait for a Win32 fix if you have Win32 clients). == So the package seems to be unusable by everyone who uses tapes for backups, runs a 2.6 Linux kernel and has no tape inserted in the drive when the backup starts. Of course I would love to see a fix for this problem even in Sarge if possible. Perhaps upstream can deliver a patch for the 1.36.2 version? -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages bacula-sd depends on: ii bacula-common 1.36.2-2sarge1Network backup, recovery and verif ii debconf1.4.30.13 Debian configuration management sy ii libacl12.2.23-1 Access control list shared library ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcomerr2 1.37-2sarge1 common error description library ii libgcc11:3.4.3-13GCC support library ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries ii libpq3 7.4.7-6sarge1 PostgreSQL C client library ii libssl0.9.70.9.7e-3 SSL shared libraries ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
