[rdiff-backup-users] Re: Uh-oh, IOError in 1.0.0, oh, no!

[jonathan . w . smith]

I tried following a "workaround" provided in the FAQ. I deleted the older 
current and moved the newer one to a different place, then ran the backup 
again. 

The backup failed to run and provided the following info:

Fatal Error: Bad rdiff-backup-data dir on destination side

The rdiff-backup data directory
/mnt/e3/rdiff-backup-data
exists, but we cannot find a valid current_mirror marker.  You can
avoid this message by removing the rdiff-backup-data directory;
however any data in it will be lost.

Probably this error was caused because the first rdiff-backup session into a 
new directory failed.  If this is the case it is safe to delete the 
rdiff-backup-data directory because there is no important information in it.