Package: backup-manager
Version: 0.5.8-2
Severity: important
I have a problem with writing archives to CDR(W). Backup-manager uses
the variable BM_BURNING_DEVICE both as device for cdrecord and as a
mountable device to verify the burned files. This causes problems for
me: if I set BM_BURNING_DEVICE to a device file, say /dev/cdrw, cdrecord
fails, leaving the following log (footnote 1):
scsidev: '/dev/cdrw'
devname: '/dev/cdrw'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
cdrecord: Read-only file system. Cannot open '/dev/cdrw'. Cannot open SCSI
driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrecord:
cdrecord: For more information, install the cdrtools-doc
cdrecord: package and read /usr/share/doc/cdrecord/README.ATAPI.setup .
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to <[EMAIL PROTECTED]>.
The original author should not be bothered with problems of this version.
But if I set BM_BURNING_DEVICE to "0,1,0" as in my /etc/default/cdrecord, the
burning works but not the verification, since "0,1,0" can obviously not be
mounted, as confirmed in the error message of backup-manager:
"unable to mount 0,1,0 on /tmp/bm-mnt.4oGUyF".
A workaround that worked for me: as root run (needs GNU sed 3.95 or higher)
sed -i~ 's/dev=${BM_BURNING_DEVICE}//' /usr/share/backup-manager/actions.sh
which will remove the explicit device setting for cdrecord and let
cdrecord the system's default burning device (most people will have
only one anyway)(footnote 2).
Regards,
Sven Joachim
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.31
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages backup-manager depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii gzip 1.3.5-10 The GNU compression utility
ii ucf 1.17 Update Configuration File: preserv
-- debconf information:
backup-manager/upload-key:
* backup-manager/name-format: long
backup-manager/upload-hosts:
backup-manager/upload-user-ftp:
* backup-manager/cron_frequency: daily
* backup-manager/cron_d_remove_deprecated: true
* backup-manager/blacklist: /home/sven/tmp
* backup-manager/time-to-live: 5
* backup-manager/burning-maxsize: 650
backup-manager/upload-user-scp-warning:
backup-manager/transfert_mode: scp
* backup-manager/dump_symlinks: false
backup-manager/upload-user-scp: bmngr
* backup-manager/burning-device: /dev/cdrw
backup-manager/upload-dir: /var/archives/uploads
* backup-manager/directories: /etc /home/sven
* backup-manager/filetype: tar.gz
* backup-manager/backup-repository: /var/archives
* backup-manager/burning-method: CDR
* backup-manager/burning-enabled: true
* backup-manager/cron_remove_deprecated: false
* backup-manager/want_to_upload: false
footnote 1: To actually get the log, I had to comment out the line
with "rm -f $logfile" in logger.sh. This is subject of
another bug report.
footnote 2: After I applied this patch, mounting the freshly burned CDR
and verifying the md5sums worked fine. But I got an "MD5 hash mismatch"
for files which were actually symlinks in my $BM_ARCHIVES_REPOSITORY.
Tell me if you want another bug report on that.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
