Hi!
There is no problem with SMB server. I try to simple copy all my data to it and everything is ok.
Error always happens on the same file when rdiff-backup try to rename tmp file it (see the output below). File has quite long name. Maybe this is the problem? What gzip.pyc try to do with file?
Tue Oct 07 09:01:58 2008 Renaming x:/ЕТА/Методология/Отчетные документы/Этап_2
Рабочий проект/07.02.26/pdf`s/Том 6.2/rdiff-backup.tmp.2237 to x:/ЕТА/Методологи
я/Отчетные документы/Этап_2 Рабочий проект/07.02.26/pdf`s/Том 6.2/Регистр. карто
чка.pdf
Tue Oct 07 09:01:58 2008 Exception '[Errno 9] Bad file descriptor' raised of cl
ass '<type 'exceptions.IOError'>':
File "rdiff_backup\Main.pyc", line 302, in error_check_Main
File "rdiff_backup\Main.pyc", line 322, in Main
File "rdiff_backup\Main.pyc", line 278, in take_action
File "rdiff_backup\Main.pyc", line 344, in Backup
File "rdiff_backup\backup.pyc", line 38, in Mirror
File "rdiff_backup\backup.pyc", line 230, in patch
File "rdiff_backup\rorpiter.pyc", line 177, in FillInIter
File "rdiff_backup\backup.pyc", line 103, in get_diffs
File "rdiff_backup\backup.pyc", line 166, in get_sigs
File "rdiff_backup\backup.pyc", line 326, in next
File "rdiff_backup\backup.pyc", line 367, in shorten_cache
File "rdiff_backup\backup.pyc", line 417, in post_process
File "rdiff_backup\metadata.pyc", line 442, in write_object
File "rdiff_backup\metadata.pyc", line 401, in write_object
File "rdiff_backup\metadata.pyc", line 395, in write_record
File "rdiff_backup\rpath.pyc", line 1420, in write
File "gzip.pyc", line 205, in write
Traceback (most recent call last):
File "rdiff-backup", line 23, in <module>
File "rdiff_backup\Main.pyc", line 302, in error_check_Main
File "rdiff_backup\Main.pyc", line 322, in Main
File "rdiff_backup\Main.pyc", line 278, in take_action
File "rdiff_backup\Main.pyc", line 344, in Backup
File "rdiff_backup\backup.pyc", line 38, in Mirror
File "rdiff_backup\backup.pyc", line 230, in patch
File "rdiff_backup\rorpiter.pyc", line 177, in FillInIter
File "rdiff_backup\backup.pyc", line 103, in get_diffs
File "rdiff_backup\backup.pyc", line 166, in get_sigs
File "rdiff_backup\backup.pyc", line 326, in next
File "rdiff_backup\backup.pyc", line 367, in shorten_cache
File "rdiff_backup\backup.pyc", line 417, in post_process
File "rdiff_backup\metadata.pyc", line 442, in write_object
File "rdiff_backup\metadata.pyc", line 401, in write_object
File "rdiff_backup\metadata.pyc", line 395, in write_record
File "rdiff_backup\rpath.pyc", line 1420, in write
File "gzip.pyc", line 205, in write
IOError: [Errno 9] Bad file descriptor
close failed: [Errno 9] Bad file descriptor
2008/10/3 Andrew Ferguson
<address@hidden>
On Oct 3, 2008, at 12:24 AM, Всеволод Витязев wrote:
Hi
If I turn off logging i get another error ....
Thu Oct 02 15:26:31 2008 Exception '[Errno 9] Bad file descriptor' raised of cl
ass '<type 'exceptions.IOError'>':
File "rdiff_backup\Main.pyc", line 302, in error_check_Main
File "rdiff_backup\Main.pyc", line 322, in Main
File "rdiff_backup\Main.pyc", line 278, in take_action
File "rdiff_backup\Main.pyc", line 344, in Backup
File "rdiff_backup\backup.pyc", line 38, in Mirror
File "rdiff_backup\backup.pyc", line 230, in patch
File "rdiff_backup\rorpiter.pyc", line 177, in FillInIter
File "rdiff_backup\backup.pyc", line 103, in get_diffs
File "rdiff_backup\backup.pyc", line 166, in get_sigs
File "rdiff_backup\backup.pyc", line 326, in next
File "rdiff_backup\backup.pyc", line 367, in shorten_cache
File "rdiff_backup\backup.pyc", line 417, in post_process
File "rdiff_backup\metadata.pyc", line 442, in write_object
File "rdiff_backup\metadata.pyc", line 401, in write_object
File "rdiff_backup\metadata.pyc", line 395, in write_record
File "rdiff_backup\rpath.pyc", line 1420, in write
File "gzip.pyc", line 205, in write
These errors are not windows-specific, as far as I can tell. They are indicating that rdiff-backup is having trouble writing a particular file. The previous errors you posted are similar.
I suggest you add the "-v 5" option (no quotes) when running rdiff-backup. Then, you can see which file it is working on immediately before the error happens.
Since you are getting an error about a "Bad file descriptor", the error could be due to all sorts of reasons, unfortunately:
- Network timeout
- SMB server out of resources
- Client system out of resources
- Hardware issues: memory, cpu, network
By using the -v 5 option, you can see if the error always happens on the same file, or if it happens on different files. Perhaps it always happens after the same amount of time has passed? If it always happens on the same file, you can use the --exclude options to exclude it (make sure to read the Windows README about how those options work on Windows). You could also try backing up just the folder which contains that troublesome file.
Oh, and look in the system logs on both the client and the server, there could definitely be important clues there.
Andrew