Re: [Duplicity-talk] Problem with "wb" mode on a FAT32 partition

[Kenneth Loafman]

Marcin Zajączkowski wrote:
> Hi,
>
>
> I tried to use Duplicity to backup my profiles, but I have problem
> probably related with a type of partition (FAT32). Duplicity is unable
> to create any file (IOError: invalid mode: wb).
>
> Simple backup command on a local file system with a verbosity set to 9.
>
>
> (...)
> Getting delta of (('profiles', 'default', 'vcard')
> psi/profiles/default/vcard dir) and None
> Generating delta - new file: profiles/default/vcard
> Selecting psi/psirc
> Comparing ('psirc',) and None
> Getting delta of (('psirc',) psi/psirc reg) and None
> Generating delta - new file: psirc
> Writing 
> /mnt/dosf/Mozilla/psi/psi-duplicity/duplicity-full.2007-04-06T21:36:31+02:00.vol1.difftar.gpg
> Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 373, in ?
>     if __name__ == "__main__": main()
>   File "/usr/bin/duplicity", line 366, in main
>     if not sig_chain: full_backup(col_stats)
>   File "/usr/bin/duplicity", line 142, in full_backup
>     bytes_written = write_multivol("full", tarblock_iter, globals.backend)
>   File "/usr/bin/duplicity", line 89, in write_multivol
>     backend.put(tdp, dest_filename)
>   File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line 235, in 
> put
>     target_path.writefileobj(source_path.open("rb"))
>   File "/usr/lib/python2.4/site-packages/duplicity/path.py", line 496, in 
> writefileobj
>     fout = self.open("wb")
>   File "/usr/lib/python2.4/site-packages/duplicity/path.py", line 448, in open
>     else: result = open(self.name, mode)
> IOError: invalid mode: wb
>
>
> duplicity-0.4.2
> librsync-0.9.7
>
> Is it possible to write backup on a FAT32 partition?

Yes, its possible.  I'm looking at the code for this right now and not 
seeing what could be causing a problem.  Could you tell us
 - what system you're using,
 - the full command line,
 - how the mount is done (SMB/CIFS/NFS)?

The 'wb' says to do all writes untranslated (binary), i.e. don't munge 
the line ends.  That would not be a system issue, it's part of the 
Python runtime.  My guess is that it's really a bogus error message. 
Yes, there was an error, but the mode has nothing to do with it.

Could you try creating a file on that partition with the same name as 
the one duplicity was trying to use.  Windows (I'm guessing a windows 
mount) has different filename character restrictions and the special 
chars in the filename may be causing a problem.

...Thanks,
...Ken