What kind of host is the LUN being used by? You can thin provision the 2nd LUN but that's not going to help if you're trying to mirror them.
There is generally a lot of space you can use on a filer in a pinch - just make sure to put it back after you use it (i.e. taking out reservations & aggr snapshots). Make sure you know the implications of using this space but generally I have found you can figure out ways to temporarily get the space you need unless you've got an unusual set up.
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Bob McKim Sent: Thursday, August 05, 2010 5:45 PM To: toasters@mathworks.com Subject: A couple of V-Series Questions
1) I have a customer who accidentally added a LUN to an existing aggr that was incorrectly sized. What is the correct procedure to replace that LUN with a correctly sized one? They can't resize the LUN on the existing array as it's out of space. Do I create a correct sized LUN on another array, add it as a spare and then do a disk fail against the wrong sized LUN? I've never tried this on a gateway.
2) Does anyone have some procedures for a headswap on a v-series/gfiler? There appears to be a "black hole" on the NOW site in regards to how-to upgrade a v-series/gfiler.
Is it as simple as -
1) Gather existing v-series head configuration 2) Zone and LUN mask the new v-series head to the existing LUNs 3) Perform a disk reassign ownership on an aggr by aggr basis 4) Create new CIFS shares on new v-series head (only CIFS shares on existing v-series head) 5) Remove old v-series head from DNS (or swap servers in DFS) 6) Add new v-series head to DNS 7) Verify client connectivity
Thanks
Bob McKim
Although no hardware was injured in the creation of this note, a few billion electrons and photons were utilized against their will.
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.