Couldn't find any reference to this error message on NOW:
Sun Feb 4 23:47:00 EST [drp-na1: worker_thread:error]: snapmirror: Filesystem version mismatch for destination volume nocna1_vol0, reverting the version and aborting transfer. SnapMirror will retry until this revert is complete.
That appears on a destination F840 running 6.0.1R1. Volume /vol/nocna1_vol0 on the F840 is large enough and is marked offline. "snapmirror status" shows:
Source Dest Status 192.168.50.17:vol0 drp-na1:nocna1_vol0 Idle
Filer 192.168.50.17 is an F740 running 5.3.6R2. It prints this to syslog:
Sun Feb 4 23:29:18 EST [worker_thread]: snapmirror: Destination drp-na1 could not accept a complete transfer Sun Feb 4 23:49:18 EST last message repeated 20 times
What is this about filesystem versions? Is the F840 doing something about it on /vol/nocna1_vol0? How can I check on the progress of this revert operation?
I guess I should be asking: are 5.3.x and 6.0.x snapmirrors compatible? The 6.0 Data Protection Guide doesn't mention caveats or incompatibilities.
On Mon, 5 Feb 2001, Brian Tao wrote:
I guess I should be asking: are 5.3.x and 6.0.x snapmirrorscompatible? The 6.0 Data Protection Guide doesn't mention caveats or incompatibilities.
Patience pays off, I guess. I let the filers mull over their purpose in life overnight, and come morning, they were happily snapmirroring away. Looking in the logs:
[1] Sun Feb 4 23:20:00 EST [drp-na1: worker_thread:error]: snapmirror: destination volume nocna1_vol0 is on-line and not in snapmirrore d state, aborting transfer [2] Sun Feb 4 23:20:43 EST [drp-na1: raid_admin:notice]: RAID checksum upgrade phase 1 (of 2) on volume nocna1_vol0 aborted. [3] Sun Feb 4 23:23:00 EST [drp-na1: worker_thread:error]: snapmirror: Filesystem version mismatch for destination volume nocna1_vol0, reverting the version and aborting transfer. SnapMirror will retry until this revert is complete. [...] [4] Mon Feb 5 00:23:48 EST [drp-na1: cksum_block_zeroer:info]: Checksum revert of volume nocna1_vol0 completed; vol copy and snapmirror now allowed.
1. I put in a snapmirror.conf and turned on snapmirror. 2. "vol offline nocna1_vol0" 3. First occurrence of the message... repeated once a minute (in accordance to my schedule in snapmirror.conf) 4. One hour to revert this filesystem. Seems to vary quite a bit on filesystem size and filer load. I haven't found any sort of progress indicator for this operation.
I haven't done much else with it yet, so there may still be 5.3.6R2 -> 6.0.1R1 caveats that I have not yet uncovered. Seems pretty slick so far though (mmmmm, fast snapshots...).
-
Brian Tao