[rdiff-backup-users] Bad filenames and files too large

[Stefan Champailler]

Hello,

While trying to reproduce a problem I had yesterday, I "made up" a whole new 
one. And a pretty interesting one I guess.

Using rdiffbackup 1.3.3.

First I create a test directory (one that I will try to back up later on). Then 
I make up some test files with the following code :

filename = "test/rdiffbackup"
#broken unicode character
filename = filename + chr(0xFF) + chr(0xFD)
filename = filename + chr(0x80) + chr(0xFF) + chr(10) + chr(13) + chr(0xC2) + 
chr(0xB0) + chr(0xC2)
filename = filename + "ABC"
file = open( filename,"w")
file.write("rdiffbackup test")
file.close()


Basically, this creates a filename with broken unicode chars in it. This might 
seem very odd but it actually happens in normal business down here in 
Europe where various encodings exist (e.g. a filename initially created CP1252 
on Windows, then uploaded on a Solaris server set up with UTF8 and 
donwloaded back on my ISO-8859-1 ext2 filesystem...)

I make an initial back up of the test directory on a USB drive, vfat formatted. 
Looks good.

Afterwards, in the test directory I  add a nice 6gigabytes ISO file.

I run rdiff again (no fancy option, no tricks, just rdiffbackup source dest).

First the backup fails : the ISO file is too large. Surprising because :

address@hidden:~$ df -h /media/LACIE-1/
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              75G   47G   29G  62% /media/LACIE-1

I guess the issue is a limitation of a VFAT filesystem.


Then I start the back up again. Got this :

address@hidden:~$ rdiff-backup-1.3.3/install/bin/rdiff-backup ~/test 
/media/LACIE-1/trd
Warning: hard linking not supported by filesystem at 
/media/LACIE-1/trd/rdiff-backup-data
Previous backup seems to have failed, regressing destination now.
Warning, repeated index ('rdiffbackup\n\r\xc2\xb0',), bad filesystem?
Warning, repeated index ('rdiffbackup\n\r\xc2\xb0ABC',), bad filesystem?
Warning: Could not restore file rdiffbackup����
°�!

You recognize the specially crafted file rdiffbackup???... + some more files 
with other bad filenames I created before. I also got a file too large error 
for the ISO file which is OK.

Then I try again, same errors. OK, predictable.

Then I try to remove the backup directory to start from scratch :

address@hidden:~$ rm -R /media/LACIE-1/trd
rm: cannot remove `/media/LACIE-1/trd/rdiffbackup;010;013°': No such file or 
directory
rm: cannot remove `/media/LACIE-1/trd/testrdiffbackup¢': No such file or 
directory
rm: cannot remove `/media/LACIE-1/trd/rdiffbackup;010;013°;065;066;067': No 
such file or directory

I don't get this. So I list the files :

address@hidden:~$ ls -al /media/LACIE-1/trd
ls: cannot access /media/LACIE-1/trd/rdiffbackup;010;013°: No such file or 
directory
ls: cannot access /media/LACIE-1/trd/rdiffbackup;010;013°;065;066;067: No such 
file or directory
ls: cannot access /media/LACIE-1/trd/testrdiffbackup¢: No such file or directory
ls: cannot access /media/LACIE-1/trd/rdiffbackup;010;013°: No such file or 
directory
ls: cannot access /media/LACIE-1/trd/rdiffbackup;010;013°;065;066;067: No such 
file or directory
ls: cannot access /media/LACIE-1/trd/testrdiffbackup¢: No such file or directory
total 64
drwxr-xr-x  2 stefan root 32768 2010-01-03 13:52 .
drwxr-xr-x 12 stefan root 32768 2010-01-03 13:51 ..
-?????????  ? ?      ?        ?                ? rdiffbackup;010;013°
-?????????  ? ?      ?        ?                ? rdiffbackup;010;013°
-?????????  ? ?      ?        ?                ? 
rdiffbackup;010;013°;065;066;067
-?????????  ? ?      ?        ?                ? 
rdiffbackup;010;013°;065;066;067
-?????????  ? ?      ?        ?                ? testrdiffbackup¢
-?????????  ? ?      ?        ?                ? testrdiffbackup¢
address@hidden:~$ 


which is basically the strangest thing I've ever seen :-)

In case you wonder, the backup filesystem (USB) is mounted like this (automount 
on my Debian, I didn't set up anything particular):


/dev/sdb1 on /media/LACIE-1 type vfat 
(rw,nosuid,nodev,noatime,uhelper=hal,flush,uid=1000,utf8,shortname=lower,iocharset=iso8859-1)



That 's not entirely blocking for me so rdiffbackup is still useful, but I'd be 
happy to understand what went wrong :-)

Stefan




-- 
Timeo Danaos et dona ferentes