I have a VNX5500 Unified that we are using primarily for CIFS shares. At one time a Raid group was created with the wrong number of disks (6 vs 8, Raid 6) leaving us with 2 extra disks and a small Raid Group. We are working to move all the file systems that are using that Raid Group off to other locations so we can rebuild it correctly. Does anyone know of a way that we can create a file system in the same 'storage pool for file' and tell it to either use specific volumes or not use specific volumes.
My thought is that if I could do that I could create the destination file systems in the same pool without having to be concerned that it will use the volumes we are trying to evacuate from.
Or is there a way to tell the system to not use those volumes for any new file systems, but allow the systems that are currently there to continue to function?
Can you elaborate on how I would do that? If I could create a dummy file system on that volume specifically I would think I could use the same process to create the destination file system on another volume?
Basically instead of specifying a pool you specify a meta
See the AVM and MVM manuals for example
I would do it this way of excluding the ones you don’t want so that you still get the normal AVM behavior for striping and auto-extend for your production fs
From what I can see, since the disk is already involved with AVM and has vols/slices on it I don't have any way to create a file system on it using MVM.
jason_mills
8 Posts
652
0
Posted June 17th, 2015 11:00
Can you elaborate on how I would do that? If I could create a dummy file system on that volume specifically I would think I could use the same process to create the destination file system on another volume?