Hi again! Well, using debug logging I've got some understanding... The problem is that files and directories on bricks has inconsistent inode numbers for new 1.3.x GlusterFS. Different files don't allowed to have the same inodes, which is typical situation in unifed GlusterFS 1.2 volume. The question is, what is the client behavior in such a case? It could happen on working system, if one create a file on backend FS for example... And the more practical question: Is there a way to convert FS without recreating file structure? In my case, the data on GlusterFS 1.2 is too large to be saved on one HDD and then moved on new gluster storage... Thanks in advance for any comments. WBR, Andrey 2007/10/23, NovA <av.nova@xxxxxxxxx>: > > I'm trying to switch my GlusterFS unify storage from 1.2.tla184 to the > new 1.3.tla524... First attempt I've described earlier ( > http://lists.gnu.org/archive/html/gluster-devel/2007-09/msg00004.html > ), but I couldn't experiment on production system till now. > > So, I have working setup for 1.2.х GlusterFS unify with a lot of data > scattered on 10 servers. I want to replace GlusterFS to 1.3.x and keep > all data. Is this possible? > > Now I've just updated FUSE to 2.7.0-glfs5, reinstalled GlusterFS, > changing spec files appropriately (see previous post) and got several > strange behaviors
