2 things stand out in your message.
1. Reducing snap reserve does not contain snapshot usage. Snapshots will take up as much space as they need regardless of snap reserve size. What snap reserve does is contain the active file system blocks to a certain amount of space. This is an important concept in SnapShot planning.
2. It would be good to see the output of a snap reserve command from each filer. Something looks a little off. Becuase it seems that you adjusted the snap reserve AFTER the snap mirror occured because as I read it below, your sources are larger than your destinations and that is not possible with SnapMirror.
3. A sysconfig -r would also be useful just to match eveything up.
While some volumes of different sizes work with SnapMirror, the simplest way to implement SnapMirror is to simply set up each source and destination the same way (if possible) so that it's easy to compare sizes properly. I realize that this isn't always possible, but if you have the opportunity to do it, it makes life easier.
-- Adam Fox NetApp Professional Services, NC adamfox@netapp.com
why do we got those outputs ? Any idea ? Any experience with the df command snap reserve 5 and snapmirror ? All of this run on 5.3.7R3, F740.
Netapp 1 : << ===== DF ===== Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 150937460 137664288 13273172 91% /vol/vol0/ /vol/vol0/.snapshot 7944076 1473572 6470504 19% /vol/vol0/.snapshot /vol/mir_vol0/ 62593232 155988 62437244 0% /vol/mir_vol0/ /vol/mir_vol0/.snapshot 15648304 510236 15138068 3% /vol/mir_vol0/.snapshot
Netapp2 : << ===== DF ===== Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 74329460 155988 74173472 0% /vol/vol0/ /vol/vol0/.snapshot 3912076 510236 3401840 13% /vol/vol0/.snapshot /vol/mir_vol0/ 127105232 137664288 0 108% /vol/mir_vol0/ /vol/mir_vol0/.snapshot 31776304 1473572 30302732 5% /vol/mir_vol0/.snapshot