Re: [rdiff-backup-users] --override-chars-to-quote ?

[Andrew Ferguson]

Morgan Read wrote:
> When backing up to an ntfs/windows system (from ext3 with acl and ea)
> what are the (detrimental) consequences of using
> "--override-chars-to-quote".

Morgan,

The detrimental effect is that if you have both 'developer.doc' and
'Developer.doc' in the same directory on the ext3 side, then you will be
in for trouble when you backup to ntfs/windows. Since Windows
filesystems are not case-sensitive, the two different filenames will be
interpreted as the same one.

I'm not entirely sure what rdiff-backup will do. It may error, it may
not. It may just silently overwrite the previously written file. I
suppose you could run a test and see what happens.

At any rate, if you truly want to override it, then you must enforce a
case-insensitive naming policy on the ext3 side with scripts of some
sort. Or hope for the best. :-)

> Maintaining ’Developer.doc’ as ’Developer.doc’ instead of
> ’;068eveloper.doc’ will significantly cut down the length of some path
> names which are causing problems with windows/ntfs path name
> limitations.  (Not to mention keeping a mirror that is more a 'mirror'.)

Interesting. What are the ntfs path name limitations? Are you running
into a max length for filenames or a max length for path names?

Andrew

-- 
Andrew Ferguson - address@hidden