We should also check the OS and architecture. I never got a response as
to what system, OS, architecture the developers test on. Could you
please let me know?
Thanks
Anand Avati wrote:
Closer, but still no cigar..
*Adding hardware back into the network after replacing bad harddrive(s)
node1:~# glusterfsd -f /usr/local/etc/glusterfs/glusterfsd.vol
node1:~# mount -t glusterfs /usr/local/etc/glusterfs/glusterfs.vol /gtank
node3:~# ls -lR /gtank/ | wc -l
1802
node3:~# ls -lR /gtank/gluster1 | wc -l
413
node3:~# ls -lR /gtank/gluster2 | wc -l
1393
Do you know in what way gluster1 is different from gluster2? I tried
the same test what you are showing, and it fixed all of 2000 files in
my case (while before the latest git fix it was fixing only 743 files
for me, with the test you have shown above). Can you double check if
your upgrade on all the three nodes has happened fine? Also can you
send me an ls -lR output of /tank from either node2 or node3 so that I
can try to reproduce with the same directory structure and filenames?
Thanks,
Avati
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.12.2/2074 - Release Date: 04/22/09 08:49:00
