Hi. Is it possible to mix 32 (i386) and 64 (x86_64) bit bricks? If yes, what are the possible downsides? Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081204/7abc1235/attachment.html>
At 07:06 AM 12/4/2008, Stas Oskin wrote:>Hi. > >Is it possible to mix 32 (i386) and 64 (x86_64) bit bricks?I''ve been running gluster 1.4 using AFR between 64 bit and 32 bit machines. For a while I was having some problems bu tin the latest qa68 version I don''t seem to have the same problems anymore. I dont know if this is because they''re fixed, or they''re just not being logged :) but the systems seem to be working just fine at this point with that version of gluster>If yes, what are the possible downsides?what I believe was happening before was, the serial numbers on the 64 bit machine were sometimes getting higher than maxint on the 32 bit machine, so it would always and forever think that files/directories needed to be auto-healed. This was a particular problem with large directories which had constant changes (as each change would update the serial number on the directory). I''m not sure if/how they resolved this problem. My guess is, that they put in a mechanism to "reset" the serial numbers in some fashion.>Regards. >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
At 07:06 AM 12/4/2008, Stas Oskin wrote:>Hi. > >Is it possible to mix 32 (i386) and 64 (x86_64) bit bricks?I've been running gluster 1.4 using AFR between 64 bit and 32 bit machines. For a while I was having some problems bu tin the latest qa68 version I don't seem to have the same problems anymore. I dont know if this is because they're fixed, or they're just not being logged :) but the systems seem to be working just fine at this point with that version of gluster>If yes, what are the possible downsides?what I believe was happening before was, the serial numbers on the 64 bit machine were sometimes getting higher than maxint on the 32 bit machine, so it would always and forever think that files/directories needed to be auto-healed. This was a particular problem with large directories which had constant changes (as each change would update the serial number on the directory). I'm not sure if/how they resolved this problem. My guess is, that they put in a mechanism to "reset" the serial numbers in some fashion.>Regards. >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
At 07:06 AM 12/4/2008, Stas Oskin wrote:>Hi. > >Is it possible to mix 32 (i386) and 64 (x86_64) bit bricks?I''ve been running gluster 1.4 using AFR between 64 bit and 32 bit machines. For a while I was having some problems bu tin the latest qa68 version I don''t seem to have the same problems anymore. I dont know if this is because they''re fixed, or they''re just not being logged :) but the systems seem to be working just fine at this point with that version of gluster>If yes, what are the possible downsides?what I believe was happening before was, the serial numbers on the 64 bit machine were sometimes getting higher than maxint on the 32 bit machine, so it would always and forever think that files/directories needed to be auto-healed. This was a particular problem with large directories which had constant changes (as each change would update the serial number on the directory). I''m not sure if/how they resolved this problem. My guess is, that they put in a mechanism to "reset" the serial numbers in some fashion.>Regards. >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
At 07:06 AM 12/4/2008, Stas Oskin wrote:>Hi. > >Is it possible to mix 32 (i386) and 64 (x86_64) bit bricks?I''ve been running gluster 1.4 using AFR between 64 bit and 32 bit machines. For a while I was having some problems bu tin the latest qa68 version I don''t seem to have the same problems anymore. I dont know if this is because they''re fixed, or they''re just not being logged :) but the systems seem to be working just fine at this point with that version of gluster>If yes, what are the possible downsides?what I believe was happening before was, the serial numbers on the 64 bit machine were sometimes getting higher than maxint on the 32 bit machine, so it would always and forever think that files/directories needed to be auto-healed. This was a particular problem with large directories which had constant changes (as each change would update the serial number on the directory). I''m not sure if/how they resolved this problem. My guess is, that they put in a mechanism to "reset" the serial numbers in some fashion.>Regards. >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
> My guess is, that they put in a mechanism to "reset" the serial > numbers in some fashion.There were some issues in the transaction and self-heal code which have been fixed (available since qa68). But these were not related to 32/64bit issues. There have not been any known word size issues yet (Except for the possible endian issue on sparc solaris faced by rhubbel) avati