Dnia 8 stycznia 2009 13:41 "Krishna Srinivas" <krishna at zresearch.com> napisa?(a): > As Keith said you should not modify the backend directly. > > You are seeing 2nd servers files because (logs indicate) 2nd servers > directory had extended attributes > (because of some previous operations) which said that it is the > latest, hence the 1st servers files were deleted and 2nd servers files > were put in the 1st server. > > Krishna > > On Thu, Jan 8, 2009 at 5:27 PM, Keith Freedman wrote: > > you're modifying the filesystem outside of gluster so the results > > will not be what you expect. > > > > when you remove the files from the directory outside of gluster, the > > gluster extended attributes dont get updated. > > > > so when gluster is running again, and the directory accessed, it sees > > that the extended attributes are the same on both servers, but that > > one of them is missing files, so to be safe, it merges the directory > > listings.. this effectively 'returns' the files you deleted in the listing. > > when you then go to access the files, it will auto-heal the file from > > the other server since it's not on this one's underlying filesystem. > > > > in order to do a real test, you should turn off one server, then > > delete the file FROM THE GLUSTER MOUNT, then turn on the other > > server, and this will correctly auto-heal and delete the entries from > > the remote server. > > > > you should treat any underlying filesystem as a raw untouchable volume. > > you cant expect a system to manage things in the face of unexpected > > external influences. > > if the disc will fall on a single server glaster remove files from the second (good server) ? noc-xx-2:/mnt/glusterfs# echo 7 > 7 bash: 7: Input/output error noc-xx-2:/mnt/glusterfs# noc-xx-2:/mnt/glusterfs# echo 7 > 7 bash: 7: Input/output error noc-xx-2:/mnt/glusterfs# echo 7 > 7 noc-xx-2:/mnt/glusterfs# noc-xx-2:/mnt/glusterfs# ehh... if the 7 file exist only once server. on second server deleted by rm -f trac-xx-1:/var/storage/glusterfs/7 :D
