[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-talk] Re: Duplicity crashing - due to : in timestamp. But no
From: |
Eric B. |
Subject: |
[Duplicity-talk] Re: Duplicity crashing - due to : in timestamp. But no way to remove time-separator altogether? |
Date: |
Thu, 10 Apr 2008 10:24:16 -0400 |
> Eric B. wrote:
> > Hi,
> >
> > I'm not quite sure what is generating this error with duplicity. The
> > directory path that duplicity is pointing to is indeed a filename, not
> > an
> > actual directory, although its path does exist (I have checked it).
> >
> > # duplicity --no-encryption --volsize 2000 --full-if-older-than
> > W --include-globbing-filelist /etc/backup/duplicity.conf --archive-dir
> > /var/spool/duplicity/archive /
> > file:///mount/bashful/backup/duplicity/orion -v5
> >
> > Traceback (most recent call last):
> > File "/usr/bin/duplicity", line 460, in ?
> > with_tempdir(main)
> > File "/usr/bin/duplicity", line 455, in with_tempdir
> > fn()
> > File "/usr/bin/duplicity", line 441, in main
> > full_backup(col_stats)
> > File "/usr/bin/duplicity", line 155, in full_backup
> > bytes_written = write_multivol("full", tarblock_iter,
> > globals.backend)
> > File "/usr/bin/duplicity", line 99, in write_multivol
> > backend.put(tdp, dest_filename)
> > File
> > "/var/tmp/duplicity-0.4.9-0.fdr.6-root-root/usr/lib/python2.4/site-packages/duplicity/backends.py",
> > line 276, in put
> > File
> > "/var/tmp/duplicity-0.4.9-0.fdr.6-root-root/usr/lib/python2.4/site-packages/duplicity/path.py",
> > line 496, in writefileobj
> > File
> > "/var/tmp/duplicity-0.4.9-0.fdr.6-root-root/usr/lib/python2.4/site-packages/duplicity/path.py",
> > line 448, in open
> > IOError: [Errno 20] Not a directory:
> > '/mount/bashful/backup/duplicity/orion/duplicity-full.2008-04-09T13:10:16-04:00.vol1.difftar.gz'
>
> Duplicity requires output to a directory, not a file. Change to a
> directory and it will work.
Thanks to all for the suggestions, but after trying everything, it turned
out to be even dumber than I thought. My destination is a cifs mount, and I
had forgotten to use the mapchars mount option when mounting the cifs drive,
and hence the : in the time separators was causing me problems again. (the
server had since I had mounted it manually with the option, and I forgot to
update the entry in /etc/fstab).
So this time I figured I would try using the --time-separator option to
duplicity to ensure I don't run into this problem again in the future.
However, I wanted to simply remove the separator altogether.
# duplicity --no-encryption --volsize 2000 --full-if-older-than 1W /tmp/
file:///mount/bashful/backup/duplicity/orion/ -v5 --time-separator=''
but this causes an issue. Apparanently duplicity *requires* a time
separator of some sort? Is there no way to remove the time-separataor
character altogether?
Traceback (most recent call last):
File "/usr/bin/duplicity", line 460, in ?
with_tempdir(main)
File "/usr/bin/duplicity", line 455, in with_tempdir
fn()
File "/usr/bin/duplicity", line 441, in main
full_backup(col_stats)
File "/usr/bin/duplicity", line 153, in full_backup
sig_outfp = get_sig_fileobj("full-sig")
File "/usr/bin/duplicity", line 140, in get_sig_fileobj
fh = globals.backend.get_fileobj_write(sig_filename)
File
"/var/tmp/duplicity-0.4.9-0.fdr.6-root-root/usr/lib/python2.4/site-packages/duplicity/backends.py",
line 220, in get_fileobj_write
AssertionError: Filename
duplicity-full-signatures.2008-04-10T102051-0400.sigtar.gz not correctly
parsed
Thanks,
Eric