Navicli Storagepool Initialisation Status

Its not because its still initializing

The storage pool itself need some space for metadata which is currently not reflected in the size display

Try creating a LUN that is around 2% smaller than the pool size

Rainer

Hi,

thanks, but when I choose MAX Capacity i thought that the VNX is calculating the metadata space or overhead itself.

Its my understanding that its currently not displayed or computed correctly

Yes, it is not computed correctly.

But I have read in the VP Release Notes, that this is a known problem and should be solved in a later Flare release.

For the customer the handling is a little bit strange.

For example; we have a pool with 6TB and want to make a LUN in this pool with 6 TB. So this doesn´t work. I have to make a LUN with about 59.. GB. So I have no idea about the max usable capacity in this pool and have to try to get the max out oof this pool.

There is a formel: Consumed LUN Capacity = (User Consumned Capacity * 1,02) +3GB.

Hi Rainer,

we decided to use Raidgroups, because we don´t want to use fastvp, thin or compression.

So it is better to use rg´s because these are more flexible regarding RaidGroup Size.

But I didn´t find a CLI command that shows me the status of the initialization process for rg´s too.

We build a rg and all the disk are flashing, so i want to know how long it takes as the RG is completely built and has the full performance.

If you are consuming every last bit of your pool with just one LUN than maybe you should be using traditional raidgroups.

Remember that most of the pool features like FAST VP, compression, LUN expansion, … do need a bit of free space in the pool to work

Rainer

Hi,

I tried the getsniffer command, but no result.

LOGICAL UNITS OWNED BY SP A:

VERIFY RESULTS FOR UNIT 1

Sniffing state:                 ENABLED
Sniffing rate (100 ms/IO):      10
Background verify priority:     Medium

Historical Total of all Non-Volatile Recovery Verifies (0 passes)
-----------------------------------------------------------------
                    Corrected      Uncorrectable
Checksum errors         0               0
Write Stamp errors      0               0
Time Stamp errors       0               0
Shed Stamp errors       0               0
Coherency errors        0               0

Currently Running Full Unit Verify
-----------------------------------------------------------------
Verify State:           Idle
Percent Complete:       0
                    Corrected      Uncorrectable
Checksum errors         0               0
Write Stamp errors      0               0
Time Stamp errors       0               0
Shed Stamp errors       0               0
Coherency errors        0               0

Most Recently Completed Full Unit Verify
-----------------------------------------------------------------
                    Corrected      Uncorrectable
Checksum errors         0               0
Write Stamp errors      0               0
Time Stamp errors       0               0
Shed Stamp errors       0               0
Coherency errors        0               0

Historical Total of All Full Unit Verifies (0 passes)
-----------------------------------------------------------------
                    Corrected      Uncorrectable
Checksum errors         0               0
Write Stamp errors      0               0
Time Stamp errors       0               0
Shed Stamp errors       0               0
Coherency errors        0               0

How about navicli –getsniffer

EMC Unified Best Practices for Performance and Availability: Common Platform and Block O.E. 31.0 in the 'Binding LUNs' section describes the process and rates for each step.  You can make an estimate from the rates provided.  It also describes how Fast Bind lets you use the LUN immediately. 

For example, depending on disk type and state, the drive zeroing rate ranges from 20 MB/s to 50 MB/s.

VNX Best Practices is available on Powerlink.

can you redirect navicli getall to a file and poke around in there.

I can´t belive that is not possible to check the status of the initialisation or verify after building a raidgroup.

Each low end raid controller has this option....

Of course there is a navicli zerodisk command to check status but it requires engineering mode / password

Rainer

What is this cli command, I know the engineering password

In the cli referenz manual I can´t find this

As usual

Navicli … -scope 0 zerodisk - all status

HI,

I have the solution:

naviseccli -h IP -User sysadmin -password sysadmin -scope 0 getsniffer -"egineering-password" -rg 4 -curr

shows the following:

Currently Running Full Unit Verify

-----------------------------------------------------------------

Verify State:           Background Verify Running

Percent Complete:       21

                    Corrected      Uncorrectable

Checksum errors         0               0

Write Stamp errors      0               0

Time Stamp errors       0               0

Shed Stamp errors       0               0

Coherency errors        0               0