On Wed, Feb 15, 2012 at 6:21 AM, Carlos Carvalho car...@fisica.ufpr.brwrote:
filename overflows max-path len by 1: path
Count the characters in the displayed path and you'll see what the
max_path value is. That message is output by the sender, and indicates
names that are too long to put into
In the latest 3.1 I get this in our backup:
filename overflows max-path len by 1: path
filename overflows max-path len by 1: path
filename overflows max-path len by 9: path
filename overflows max-path len by 7: path
filename overflows max-path len by 4: path
filename overflows max-path len by 5:
Benjamin R. Haskell (rs...@benizi.com) wrote on 15 February 2012 09:46:
On Wed, 15 Feb 2012, Carlos Carvalho wrote:
In the latest 3.1 I get this in our backup:
filename overflows max-path len by 1: path
filename overflows max-path len by 1: path
filename overflows max-path len by 9:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems possible that it is the temporary file name. That would be
easy to test. Find the longest filename (or any that fails) and
attempt to touch a file with the temporary name that rsync would use.
If that is the problem then --inplace would be
Kevin Korb (k...@sanitarium.net) wrote on 15 February 2012 15:12:
It seems possible that it is the temporary file name.
Yes. After sending the other message I noticed that the amounts rsync
lists as exceeding max-path cannot be explained by a prefix at the
sender:
Carlos Carvalho
