2012-08-26 03:01 AM
Hello, i've create a new thin volume called "DS2" to replace an old one called "vmware01" then i've start to moving all Vm's inside volume "vmware01" to new one "DS2" by Vcenter storage motion, but now the Aggregate is full and i can't access to a lot of VM's. I'm in the panic!
I've space in another filer, can i try to move the volume to another filer by this command ? :
ndmpcopy -sa <user>:<pass> -da <user>:<pass> source_filer:/vol/vol_source_name/folder/file destination_filer:/vol/vol_dest_name/file
This is the result of a df command:
Filesystem kbytes used avail capacity Mounted on
/vol/vol0/ 158387408 5784652 152602756 4% /vol/vol0/
/vol/vol0/.snapshot 8336176 0 8336176 0% /vol/vol0/.snapsh ot
/vol/vmware01/ 2147483648 1796876604 0 100% /vol/vmware01/
/vol/vmware01/.snapshot 0 0 0 ---% /vol/vmware01 /.snapshot
/vol/DS2/ 1616117760 525325292 0 100% /vol/DS2/
/vol/DS2/.snapshot 0 0 0 ---% /vol/DS2/.snapsho t
/vol/DS1/ 1616117760 756281724 0 100% /vol/DS1/
/vol/DS1/.snapshot 0 0 0 ---% /vol/DS1/.snapsho t
2012-08-27 02:53 PM
If you aren't fired yet you could always try lowering your aggregate snap reserve to something lower than 5% (if its not at 0% already!) on the affected aggregate to give you some breathing room while you move data around. This has got me out of trouble a few times although it was on a snapmirror destination so no production workloads running.
A day has passed so I think you would have sorted this by now, No?
2012-08-28 07:16 AM
Are we talking about NFS datastores or iSCSI/FC LUNs?
For the former scenario, changing the volume guarantee of the original datastore to "none" can solve the issue (if it is currently set to "volume")
2012-08-28 07:23 AM
"snap reserve –A aggr03 0"
replace aggr03 with the name of the aggregate! This will free up 5% for you!! Report back with any additional questions!!
WE'RE GOING TO GET THROUGH THIS!