That is because df shows the filesystem size.  This will grow when you perform a snapmirror update.  Vol size will show the size of the volume.

--JMS

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Iluhes
Sent: Wednesday, June 05, 2013 9:40 AM
To: Gelb, Scott; Toasters
Subject: Re: growing a vol on vFiler that is a source in Vfiler DR relationship

What I dont understand is this. When i set it on destination, is not reflected by DF command

vol size: Flexible volume 'vol1' size limit set to 5800g

netapp02> df -m

Filesystem               total       used      avail capacity  Mounted on

/vol/vol1/  4618854MB  2797231MB  1821622MB      61%  /vol/vol1/

---

From: "Gelb, Scott" <sgelb@insightinvestments.com>
To: Iluhes <iluhes@yahoo.com>; Toasters <toasters@teaparty.net>
Sent: Wednesday, June 5, 2013 12:37 AM
Subject: RE: growing a vol on vFiler that is a source in Vfiler DR relationship

The SnapMirror rules apply the same so you can grow the target volume to the new size, then grow the source and the next snapmirror update will update the fs_size_fixed on the target.  There is no special procedure and you can grow the volumes the same as if no vfiler dr.  If you add a volume additional networking to the source vFiler, then you would need to create the volume and restrict it on the target and run a dr resync, but in this case there isn’t a new resource so just “vol size” on both sides.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Iluhes
Sent: Tuesday, June 04, 2013 6:25 PM
To: Toasters
Subject: growing a vol on vFiler that is a source in Vfiler DR relationship

Hello Toasters,

What is the best procedure to grow a volume on the vFiler that is a source in VFiler DR setup.

Is there a need to break / queues replication somehow