search for: 1542180

...eaded process ?). My current inclination is to blame rsync because it does an unconditional getcwd during startup, which now fails if the current directory is unreachable. Further references: https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html https://bugzilla.redhat.com/show_bug.cgi?id=1542180 Andreas Schwab agrees that rsync is buggy: https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html Thanks, Florian

...nclination is to blame rsync because it does an unconditional > getcwd during startup, which now fails if the current directory is > unreachable. > > Further references: > > https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html > https://bugzilla.redhat.com/show_bug.cgi?id=1542180 > > Andreas Schwab agrees that rsync is buggy: > > https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html > > > Thanks, > Florian > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://lists.glus...

(resending, sorry for duplicates) On 01/24/2018 05:59 PM, Dietmar Putz wrote: > strace rsync : > > 30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 getdents(3, /* 0

...c because it does an unconditional getcwd during startup, which now fails if the current directory is unreachable. Further references: https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html[https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html] https://bugzilla.redhat.com/show_bug.cgi?id=1542180 Andreas Schwab agrees that rsync is buggy: https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html[https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html] Thanks, Florian _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org[mailto:Gluster...

Hi all, i have made some tests on the latest Ubuntu 16.04.3 server image. Upgrades were disabled... the configuration was always the same...a distributed replicated volume on 4 VM's with geo-replication to a dist. repl .volume on 4 VM's. i started with 3.7.20, upgrade to 3.8.15, to 3.10.9 to 3.12.5. After each upgrade i have tested the geo-replication which worked well anytime. then i