Hi Ken, Thanks for the response. As I said, the problem is usually caused by the drive not settling quickly enough. For the writes, I can simply wait 30 sec between inserting the disk and responding to the prompt. The consistency check fails less often due to this, although I do occasionally get failures due to bad writes. At any rate, the option to retry would make this go much smoother.
I do not have a SF account. Thanks again, Jan On Sat, Jan 02, 2010 at 06:59:16PM -0600, Kenneth Pronovici wrote: > Hi Jan, > > Thanks for the bug report. Sorry that you're seeing problems writing the > disk... I haven't heard of that happening before. I will look at these > enhancements when I find a little time. > > Would you be willing to submit this bug at SourceForge? That's usually > where I track bug reports that are not specific to Debian. If not, i.e. if > you don't have a SF login, that's fine... I can do it myself. It's better > for you to own the bug, since it's your request. > > Thanks, > > KEN > > On Fri, Jan 1, 2010 at 2:37 PM, Jan Medlock > <medlock-deb...@turboshower.net>wrote: > > > Package: cedar-backup2 > > Version: 2.19.4-2 > > Severity: wishlist > > > > > > First, thanks for writing and maintaining cedar-backup2. I have found > > it very useful for regular backups. > > > > I use cback-span regularly and often have failures in either starting > > writing the disk or in mounting the disk for the consistency check. > > In both cases, I believe the failure is just due to the drive not > > settling quickly enough. These failures necessitate restarting the > > whole process and burning a whole new set of disks, which can be > > wasteful of both time and DVD+R's if I'm on one of the last disks of a > > big backup. > > > > I request new features to catch these failures and allow retrying of > > the events. In particular, > > > > 1. If the writing fails (for any reason, not just failure to start > > writing), the option of restarting the write should be given. > > (This would allow the user to insert a new medium, if necessary.) > > > > 2. If the consistency check fails (again, for any reason), allow the > > user to either, > > A. Re-run the consistency check, or > > B. Re-write the disk (again, possibly with a new medium). > > > > Thanks again, > > Jan Medlock > > > > -- System Information: > > Debian Release: squeeze/sid > > APT prefers unstable > > APT policy: (500, 'unstable'), (500, 'testing') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > > > Versions of packages cedar-backup2 depends on: > > ii python 2.5.4-5 An interactive high-level > > object-o > > ii python-support 1.0.6 automated rebuilding support > > for P > > > > Versions of packages cedar-backup2 recommends: > > pn cdrecord <none> (no description available) > > ii cedar-backup2-d 2.19.4-2 local and remote backups to CD > > or > > ii dvd+rw-tools 7.1-6 DVD+-RW/R tools > > ii eject 2.1.5+deb1+cvs20081104-7 ejects CDs and operates > > CD-Changer > > pn mkisofs <none> (no description available) > > pn ssh <none> (no description available) > > > > Versions of packages cedar-backup2 suggests: > > ii gnupg 1.4.10-2 GNU privacy guard - a free PGP > > rep > > pn grepmail <none> (no description available) > > ii mysql-client-5.1 [mysql-clien 5.1.41-3 MySQL database client binaries > > pn postgresql-client <none> (no description available) > > pn subversion <none> (no description available) > > > > -- no debconf information > > > > > > > > > -- > Kenneth J. Pronovici <prono...@ieee.org> > http://www.cedar-solutions.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
