On Thu, 30 Nov 2000, Moshe Linzer wrote:
Y'know, I didn't get any error message that the mirror failed, but the df showed the volume at 103% and the used space wasn't equal to the source volume, so I assumed that the mirror had failed due to lack of space. Now you are saying that it might have been only cosmetic - that just the df information was wrong, but the data was copied in full. Maybe, but how am I to know? We are at 5.3.6R2 by the way.
If the snap reserve values are different for the two volumes, then that implies that your df output is going to be screwy. SnapMirror will announce when a transfer cannot complete due to lack of space. The output will be in the form of a system error log:
snapmirror: destination volume too small
To verify that data was copied, you can use snap list to ensure that the latest snapshot on the destination matches up with a SnapMirror-created snapshot on the source side. Or you can mount the destination volume and peek at the files there.
As reported in my previous email, this is a bug that was fixed in 6.0. Once again, here is the public report for 18560:
TITLE: Snapreserve value not propagated to snapmirror destination
DESCRIPTION: Snapreserve value not propagated to snapmirror destination. This will cause df numbers to look quite different between the source and destination.
WORKAROUND: Don't worry about it. It actually has no affect on whether SnapMirror will function. It is more of a cosmetic thing.
Hope that helps!
-- Shane
------- It's always a good idea to bypass NVRAM.