Taking extreme measures, I went through my home directory and deleted all the files from the underlying storage bricks which refused to self-heal and then allow them to repropagate via unison. This seemed to work for a while, however while running the latest TLA code I've all of a sudden got exactly the same problem back on the exact same files. Log (which includes spec files) is attached. Unison is running via an SSH login to my personal user account, so I don't think that's the problem - this seems to be some type of persistent bug. I'm also having some rather more disturbing issues of data going missing for no good reason - while it's possible a user is deleting it, it seems pretty unlikely. Are there any circumstances under which this could happen without actual delete commands being issued? - Will Rouesnel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20080731/34e3c638/attachment-0001.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: glusterfs.log Type: application/octet-stream Size: 964845 bytes Desc: not available Url : http://zresearch.com/pipermail/gluster-users/attachments/20080731/34e3c638/attachment-0001.obj
