Dnia 9 stycznia 2009 11:03 Keith Freedman <freedman at FreeFormIT.com> napisa?(a): > >As you can see the files replicated themselves but only after the > >third attempt to open the file on a client. As I understand I > >shouldn't remove the file directly on the server but such situation > >might occur. Perhaps the scenarion should be addressed somehow? > > yes, I'd agree with this.. the I/O error shouldn't happen. gluster > should figure out the files missing, determine whether or not it > should be there or not there, and then fix before reporting back an I/O error. > > again, what version of gluster are you using. I remember running > into this a while ago, and the problem was resolved. > > what I'm seeing in 1.4.0.patch-824 is the following: > > I removed a file from the underlying filesystem on server A. > I did an LS of the mounted filesystem on server a, and it was there, > I did a cat of the file and it was there. > but when I look for it in the underlying filesystem it's not there. > so, it knows it's not on the local volume, and it gets it from the > other server, but it doesn't auto-heal the file back? > this seems like a bug, but I defintiely didn't get the I/O error you saw. > > > I use: glusterfs 1.4.0rc7 built on Jan 7 2009 15:00:10 Repository revision: glusterfs--mainline--3.0--patch-814
