> > > Since glusterfs is so flexible/configurable, I suspect > that any substantial deployment will have to deal with > this at some point. Anytime a client mounts shares > from two different servers it is likely to run into > this problem. Should glusterfs perhaps develop a > strategy for administrators to deal with this in a > simple way? Whether that be by suggesting a certain > package management strategy to distributors (allowing > mulitiple glusterfs client packages to be installed on > the same machine), or by making the client binaries > become backwards compatible? I fear that without a > clean (and easy) solution to this serious admins might > shy away from deploying glusterfs in production > environments. Thoughts? > > Martin, Yes! we know that is a limitation as of now. We have aim to have backward compatibility from 1.5.x releases. But currently 1.3 -> 1.4 doesn't work fine. (and even 1.4.0qaXX releases may not work with other 1.4.0qa releases as there may be some changes in APIs internally. Regards, Amar
