Thanks Nicolas for your quick reply. Really sorry about the long delay in replying back, I was away and was busy with so many things. Anyway I checked the file system using scandisk but did not find any errors. Also I guess if the file system has errors even initial backup should fail. But in this case if I delete the destination directory the backup works properly, this happens only for incremental.
I wonder whether this is a bug in rdiff-backup. For me it seems more like that rdiff-backup is having some problems with NTFS permission (read only etc.) Anyway this is just my guess.
Thanks again,
bye,
Suneth.
#avg_ls_inline_popup{position: absolute;z-index: 9999;padding: 0px 0px;margin-left: 0px;margin-top: 0px;overflow: hidden;word-wrap: break-word;color: black;font-size: 10px;text-align: left;line-height: 130%;}
). And this is a file name so I do not understand why Sarel talks about typing in word. I mean nothing was typed in word. Anyway I do accept and understand that there seems to be something wrong with this character. But my point is how did it get backed up initially in the first time? and doesn't that mean that rdiff-backup can handle it somehow? at least in the initial backup though not in incremental?. My real concern is that I am talking about many gigs of data here even if I rename this file to something simple as abc there is a chance for some other file to have characters like this.
