I have a mapped 'storage pool for file' called 'Pool 0'. As far as I can tell nothing is using it. I have tried getting rid of it manually with the command 'nas_pool -delete id=48 -Force'. This successfully completes, but the mapped Pool returns as so as I run another diskmark.
1. How do I confirm that nothing is using this mapped storage pool?
2. How do I get rid of it?
3. What are mapped storage pools for file good for anyway?
I have a block storage pool called ‘Pool 0’. As long as this remains I will always have a mapped storage pool for file of the same name?
Also, is this mapped pool allowed to be used to directly provision a file system (versus manually creating a storage pool for file and building my FS on top of that)?
2. You will need to delete the pool from the Block side as well. You can do this by navigating to Storage -> Storage Pools.
3. A mapped pool is a storage pool that is dynamically created during the normal storage discovery (diskmark) process for use on the VNX for File. It is a one-to-one mapping with a VNX Block storage pool.
Make sure there are no file system in use (nas_fs -l), list all dvols (nas_disk -l) and make sure inuse column has an "n". Delete dvols (nas_disk -delete dX -perm -unbind).
ocejiasa
16 Posts
560
0
Posted July 12th, 2012 14:00
I have a block storage pool called ‘Pool 0’. As long as this remains I will always have a mapped storage pool for file of the same name?
Also, is this mapped pool allowed to be used to directly provision a file system (versus manually creating a storage pool for file and building my FS on top of that)?