Partial file creation tripping up on aufs volume - tries to use a reserved name

[OmegaPhil]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24/02/14 18:35, Wayne Davison wrote:
> On Fri, Feb 21, 2014 at 8:14 AM, OmegaPhil <omegaphil at gmail.com>
> wrote:
> 
>> Other than ignoring the problem and using --inplace, it doesnt
>> look like I can influence how rsync names its temporary files -
>> is this worth a feature request?
>> 
> 
> Outside of using --inplace, you can only request that rsync put its
> temp files into a different directory (--temp-dir=FOO), but that
> isn't that nice of an option to use if the temp-dir isn't on the
> same filesystem as the destination dirs (since it's best to be able
> to rename the files into place w/o copying).
> 
> An option to change the prefix from "." to something else might be 
> reasonable.  Or you could look at the get_tmpname() function in
> receiver.c and tweak this line to use some other single character
> (e.g. ':', '_', or whatever):
> 
> fnametmp[length++] = '.';
> 
> That would allow you to do your copying w/o error at least.  If you
> want to make it longer than a single char, the code would need to
> change to check if the extra chars would fit w/o overflow.
> 
> ..wayne..


Thanks for this - I did test temp-dir previously but it didnt stop the
temporary naming from being used so I ignored it - so you're
suggesting to use a different filesystem as the temp directory
location to get around the special naming? This would be fine for the
rare reserved name but as you said, with much more common big files
that would be a serious copying overhead.

Currently rsync is managed by the package system, so I don't want to
maintain a special compile just for this freak problem, but then I
don't want to bother yourselves for a feature request that in reality
boils down to one file out of over a million. I think I'll stick to
inplace until I get more examples, and then make a feature
request/hack myself.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBAgAGBQJTDj8RAAoJEBfSPH39wvOP16sP+wedVhwFKS+8w5OCM2JYFIvb
yPSTJNWXjUSHWnCUX68keir/B0/Hp12TrMRsr6iW/SzqVv4CrwdrK9ieCnFQnMRz
WzCPeyuSj1rIk9bEVHNPj2/VnQLYx64oZSqj3Ljmvjx4occfihay40nWmZGxZd00
lZ8p4JniCK/lXIGXD9zpkneXfn22hrf9XN9yuleQ/cTv3P33jNsCVfd2JfdcIn2b
qwXC0InePRzNlwuA0KOGsKDsoyIGu4rmTa4hLJm/qdmjF/daqz5PL3zIxcZitVjX
1STVopwtUkDywFdqTcOzpAtFXOSxaIPeDb+v7efentCrgbVFwwvKOD2TpOOmz9k9
yGOOXu0VF39fKlBo00QCWuAAvyBndasWPYm1CuwdrY8HyDBuAQXOPz0zlE7xD0Fx
ZrHn38g5VuM43ZBb770PegkdhUkmPE3ORjnjmyuC0POykUb5FCj8ASTWZuYCEln6
IA2Ga3OEki++G9SN2uYWrnrOraw3e0eCMCNUnJNSO2g7S9SPXaSzl/c7cp6h/H0U
/ExANJrQyOFerjS+kmRMxbiaLu0pktI4iTc9Ek2rskDZSUrzl59yLbc27lWxvfHW
7rkzHETtLHRKufj3t7fsHUJDndFt+YlNlPMPMr4I9ZslN667ZLBRjsac00BgnoPk
XhsSR5qbYJuRpE5vG3gj
=a/Z3
-----END PGP SIGNATURE-----