On Tue, 3 Mar 2009 19:02:03 +0530, Anand Avati <avati@xxxxxxxxxxx> wrote: > On Wed, Feb 18, 2009 at 1:09 AM, Gordan Bobic <gordan@xxxxxxxxxx> wrote: >> OK, I've managed to resolve this, but it wasn't possible to resync the >> primary off the secondary. What I ended up doing was backing up the files >> that were changed since the primary went down, blanking the secondary, >> resyncing the secondary off the primary, and copying the backed up files >> back into the file system. >> >> By primary and secondary here I am referring to the order in which they >> are listed in subvolumes. >> >> So to re-iterate - syncing primary off the secondary wasn't working, but >> syncing secondary off the primary worked. >> >> Can anyone hazard a guess as to how to debug this issue further? Since I >> have the backup of the old data on the secondary, I can probably have a >> go >> at re-creating the problem (I'm hoping it won't be re-creatable with the >> freshly synced data). > > Did you happen to change the subvolume order in the vofile, or > add/remove subvols? Doing so may result in such unexpected behavior. Yes. I added a server/subvolume to the AFR cluster, and subequently removed one of the servers. Are there any additional procedures that have be followed when adding a node to a cluster? Gordan
