Scott> Yep. I was able to free up some space on a non-thin provisioned Scott> volume, and start the vol move. All good now and things are Scott> chugging along at 300MB/s Thanks for the hand holding everyone.
Glad to help, just paying forward all the help I've gotten here over the years...
Scott> On Nov 4, 2019, at 4:56 PM, Andrew Werchowiecki Andrew.Werchowiecki@xpanse.com.au wrote:
Scott> Mate you have a ~26TB aggregate that has ~1.8TB spare. Just increase the size of the volume by Scott> say 200g and immediately start the volume move. The sooner you do this the better off you will Scott> be, even though you are close to the limits already you still have some room to move. Leave it Scott> any longer and all that space may get eaten up.
Scott> Go go go do it now.
Scott> Regards,
Scott> Andrew
Scott> On 5/11/19, 8:53 am, "toasters-bounces@teaparty.net on behalf of John Stoffel" < Scott> toasters-bounces@teaparty.net on behalf of john@stoffel.org> wrote:
Scott> And the underlying aggregate is full too. I guess we relied a Scott> bit too much on thin provisioning and now need to get some Scott> volumes off the full aggregate.
Scott> This is what scares me about Thin provisioning, because when it does Scott> go south, you're in a world of hurt until you can reduce the load Scott> somehow.
Scott> Do you have any snapshots on the other volumes you can delete to make Scott> space? Or maybe you have to bite the bullet and add more disks to Scott> that Aggregate?
Scott> Cluster::> aggr show-space -aggregate-name cluster_03_sata02_8t
Scott> Aggregate : cluster_03_sata02_8t
Scott> Feature Used Used% Scott> -------------------------------- ---------- ------ Scott> Volume Footprints 25.37TB 100% Scott> Aggregate Metadata 809.8MB 0% Scott> Snapshot Reserve 0B 0% Scott> Total Used 25.37TB 100%
Scott> Total Physical Used 24.23TB 96%
Scott>
Scott> Andrew Werchowiecki Mobile: +61 422 702 339 85 Havelock St Scott> <imageac654c.PNG> Technical Team Lead Office: +61 8 9322 6767 West Perth Scott> Andrew.Werchowiecki@xpanse.com.au Fax: +61 8 9322 6077 WA 6005 Scott> www.xpanse.com.au Australia Scott> <image151e83.JPG>
Scott> On Nov 4, 2019, at 12:58 PM, Parisi, Justin Justin.Parisi@netapp.com wrote:
Scott> Vol move takes a snapshot when doing the move; that's how the transfer happens Scott> via snapmirror.
Scott> How full is the volume? Scott> Scott> ---------------------------------------------------------------------------------------------- Scott> From: Scott Classen sclassen@lbl.gov Scott> Sent: Monday, November 4, 2019 3:55 PM Scott> To: Parisi, Justin Justin.Parisi@netapp.com Scott> Cc: Toasters toasters@teaparty.net Scott> Subject: Re: Volume move.... Working?
Scott> NetApp Security WARNING: This is an external email. Do not click links or open Scott> attachments Scott> unless you recognize the sender and know the content is safe.
Scott> This volume has snapshots disabled so I’m not sure what the error is referring Scott> to.
Scott> So it looks like the job is running… maybe I just need to be patient? I just Scott> haven’t done any Scott> volume moves (other than when moving to a new filer) so am not sure what to Scott> expect in terms of Scott> speediness.
Scott> Cluster::> job show -id 11160 Scott> Owning Scott> Job ID Name Vserver Node State Scott> ------ -------------------- ---------- -------------- ---------- Scott> 11160 Volume Move Cluster node-03 Running Scott> Description: Move “bigvol" in Vserver “svm1" to aggregate Scott> “cluster_03_sata01_8t"
Scott> S
On Nov 4, 2019, at 12:45 PM, Parisi, Justin Justin.Parisi@netapp.com wrote:
If it couldn't create a snapshot, it's probably not doing a vol move.
What does "event log show" say? Job show?
-----Original Message----- From: toasters-bounces@teaparty.net toasters-bounces@teaparty.net On Behalf Of Scott
Scott> Classen
Sent: Monday, November 4, 2019 3:40 PM To: Toasters toasters@teaparty.net Subject: Volume move.... Working?
NetApp Security WARNING: This is an external email. Do not click links or open
Scott> attachments Scott> unless you recognize the sender and know the content is safe.
Hello toasters,
I’m attempting to move a 3TB vol to a new aggregate. The destination aggregate has 100TB
Scott> available space. It’s been preparing to transfer for over 3 hours…. Is this Scott> normal?
Cluster::> volume move show -vserver svm1 -volume bigvol
Vserver Name: svm1 Volume Name: bigvol Actual Completion Time: - Bytes Remaining: - Destination Aggregate: cluster_03_sata01_8t Detailed Status: Volume move job preparing transfer Error: Creating Snapshot copy with owner tag: Not enough space for Snapshot tags Estimated Time of Completion: - Managing Node: node-03 Percentage Complete: - Move Phase: replicating Estimated Remaining Duration: - Replication Throughput: - Duration of Move: 03:21:53 Source Aggregate: cluster_03_sata02_8t Start Time of Move: Mon Nov 04 09:10:19 2019 Move State: warning Is Source Volume Encrypted: false Encryption Key ID of Source Volume: Is Destination Volume Encrypted: false Encryption Key ID of Destination Volume:
Should I be concerned about the "Error: Creating Snapshot copy with owner tag: Not
Scott> enough Scott> space for Snapshot tags” ?
Is there any way to see if this vol move job is hung or actually doing something?
Thanks, Scott
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Scott> _______________________________________________ Scott> Toasters mailing list Scott> Toasters@teaparty.net Scott> http://www.teaparty.net/mailman/listinfo/toasters
Scott> _______________________________________________ Scott> Toasters mailing list Scott> Toasters@teaparty.net Scott> http://www.teaparty.net/mailman/listinfo/toasters