name too long problem?

[Kevin Korb]

-----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 a workaround.

On 02/15/12 09:21, 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:
> <path> filename overflows max-path len by 7: <path> filename
> overflows max-path len by 4: <path> filename overflows max-path len
> by 5: <path> filename overflows max-path len by 6: <path>
> 
> Both sender and receiver are linux machines, so the max-path is
> the same. Locale/lang are both set to C and --no-iconv is used. How
> can a name overflow in the receiver but exist in the sender? Can it
> be due to the temporary extension?

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk88EZsACgkQVKC1jlbQAQeiJQCeJfkps3CIMPW47iHlggSEYZLu
qqkAnjP103y9JgVauKwftlIIjUP44mZE
=nBdg
-----END PGP SIGNATURE-----