Description of problem: [root@gqac009 nfs-3]# time find pax -type d | wc -l ; time find pax | wc -l 141129 real 524m23.144s user 0m4.781s sys 0m39.305s 2215227 real 435m9.818s user 0m6.625s sys 0m44.162s [root@gqac009 nfs-3]# =========================== [root@gqac009 pax]# time du -sh * 64K home 32K lost+found 41G mnt 23M selinux real 525m1.208s user 0m3.941s sys 0m48.601s [root@gqac009 pax]# Steps to Reproduce: run: /mnt/pax# pax -v -r -w / . Allow it to run overnight or for a couple of days, this will recursively copy /mnt onto /mnt/pax. Make sure you keep a few GB of data on /mnt (assuming GlusterFS is mounted on /mnt) which is enough to create quite a depth of directory hierarchy. Setup is a four node distribute on NFS.
Deferring this to post RC. Patch available in upstream but a careful evaluation is necessary before that can be backported to release-3.3
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user