Mapping Storage Pool To File

Create LUNs on that pool and add them to the ~Filestorage Storage Group.

http://www.thulinaround.com/2012/10/15/lesser-known-enhancements-in-the-latest-vnx-code-pool-luns-for-file/

Thank you kindly for your help.....

I plan to use 2 VDM's one for NFS and another for CIFS.

I did a rescan and got the following:

Rescan Storage System All.

Discovering storage on VNX5500-CS0 (may take several minutes)

storage health check failed

APM00123403164 d7, no storage API data available

APM00123403164 d8, no storage API data available details...

Yes you do. In Unisphere click on Storage at the top and select "Rescan Storage Systems" under File Management on the right-hand side

Do I need to do a re-scan of some sort?

if you ssh to the control station and run this command "nas_disk -l" , do you see the new disks (they should match capacity of the LUN you created earlier).

I know it should but there seems be some issues.

nas_disk -l

id   inuse  sizeMB    storageID-devID   type  name          servers

1     y      11260  APM-2007 CLSTD root_disk     1,2

2     y      11260  APM-2008 CLSTD root_ldisk    1,2

3     y       2038  APM-2009 CLSTD d3            1,2

4     y       2038  APM-200A CLSTD d4            1,2

5     y       2044  APM-200B CLSTD d5            1,2

6     y      65526  APM-200C CLSTD d6            1,2

7     n      51199  APM-0064 PERF  d7            1,2

8     n      51199  APM-0065 PERF  d8            1,2

Maybe some residual crap that was leftover from a previous install. Can the above disks be removed? I have created 2 x 2TB Luns.........

you think these two are "ghost" and are not longer part of the storage group ?

7     n      51199  APM-0064 PERF  d7            1,2

8     n      51199  APM-0065 PERF  d8            1,2

That's what I am thinking.... At any rate I will delete and start fresh......... Maybe this is why the rescan fails?

I should be able to do a nas_disk -delete?

It's really Mucked up... lol

Warning 17716817789: Unbind not attempted for disk d8 with associated LUN ID=0065.

Warning 17716815737: Storage API code=38: SYMAPI_C_DB_IS_LOCKED

The SYMAPI database file is already locked by another process

Error 2201: unable to acquire lock(s), try later

Try again in 10 minutes

did it work ?

Yes it did after some time.. Thanks for the tip..... Patience is the key...