>>>>> Kevin Horton <[EMAIL PROTECTED]> >>>>> wrote the following on Tue, 1 Nov 2005 17:59:06 -0500 > > 3. The info that spews out at the start of the backup indicates that > carbonfile support defaults to OFF. I believe the default should be > ON (once carbonfile support is working), just in case that info is > important to someone. If the fact that this is ON causes an error, > and carbonfile support is not important to someone, then they can > manually turn it OFF.
Yes I agree, the default off is just a temporary thing until we can get it working. I looked up and emailed the original author so maybe he can tell me what the right thing to do here is, or point me to some documentation. > 4. The backup attempt eventually failed with a ___File name too > long___ error. ... > OSError: [Errno 63] File name too long: '/Volumes/Ext_BU/Users/kwh/ Assuming you were updating a backup started earlier, this is a good sign, since for backwards compatibility it needs to keep quoting if quoting was enabled before. However, filename too long errors should be recoverable, and not crash rdiff-backup. Perhaps you could start the python interpreter and type this in: >>> import errno >>> errno.ENAMETOOLONG 36 >>> errno.errorcode[63] 'ENOSR' (example values are what my system says---yours must be different if it is crashing rdiff-backup). -- Ben Escoto
pgpKerEOWIqSO.pgp
Description: PGP signature
_______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
