eva 6000 event an internal logical disk has transitioned to the snapshot overcommit state

[ilayy]

hi all
i have an eva 6000 after replacing a bad disk i have got the following
1) a red cross on a vdisk that appear automaticaly i didn't create it which has size 0 vraid0 and is not presented to any host and also i have no option to delete it like the attachement shows
2)in the controller event log i found an error on the same date that the vdisk was created the error is
an internal logical disk has transitioned to the snapshot overcommit state corrective action code 50
sequence :#135983
event code:09cb500S
3) at the eva level the state is: warning initialized

please assist

[Johan Guldmyr · Accepted solution]

Hey, it's not from a DR from another EVA or something like that? Maybe you need to delete it on the other side first.

Tried restart CV service?
What version of CV are you running?
Delete from SSSU?
A restart of the master controller might also do the trick.

[ilayy]

hi
i am not so expert so please if you can make it more clear for me.
yes it is true there is another eva and there is replication between them but on the other eva i have no error on any vdisk and what do you mean by DR?

[john_347]

Hi all,

If in doubt contact HP support and they can lead you through the problem. Thats what we pay support for..

regards
jc

[Johan Guldmyr]

DR / Data Replication

Maybe you have DR set up from a vdisk (that is not vraid0) on the other EVA (MVICEVA02).

And then on the EVA with the failed disk (MVICEVA01) - you set the replicated copy up as a vraid0.
When you had a disk failure on EVA2 the vraid0 obviously broke.

Just a theory. It's probably something else.

In your 1st statement you said you hadn't created anything and then in the 2nd it said that you found a snapshot error when it was created?

And yes, if you see this kind of error and don't know what it is - contact HP support. Especially if you are not so experienced with the EVA it is probably a very good idea.

[ilayy]

hi all
no i didn't create anything it appears alone and yes i have replication . between the 2 eva. as it is vraid0 and it is not presented so how i can delete it?

[Johan Guldmyr]

Tried restart CV service?
What version of CV are you running?
Delete from SSSU?
A restart of the master controller might also do the trick.

[ilayy]

one more question please if i need to do other job on the eva like creating vdisk is that present any risk?

[Johan Guldmyr]

If you want to assess your whole system for any risks, you should probably have somebody do a deep check in the logs and the configuration for you..

[ilayy]

hi all
i need to know how the continuos access work to be able to solve this problem
can you provide me some link or documents please?
i have searched the net with but nothing has been found

[Johan Guldmyr]

See here:

http://h18000.www1.hp.com/products/storage/software/conaccesseva/index.html

If you have a specific question about it maybe I can assist.

[ilayy]

hi john,
i need a document that talk about the replication because i need to know which vdisk is replicating using which schedule . the basic info about the replication

[Johan Guldmyr]

I'm not a John ;)

to find out how a vdisk is replicated you can go into each DR group and look at its members..

There's only two ways in EVA CA - synchronous or asynchronous.

I don't have a document describing the CA technologies, maybe it's available in the white paper section or in that link I posted.

[ilayy]

hi ,
johan sorry for writting your name wrong :)
guys i am confused again i looked again to the logs and the error that appears in the same day that the error on the vdisk appears is
an internal logical disk has transitioned to the snapshot overcommit state corrective action code 50
sequence :#135983
event code:09cb500S
it could be related to continous access?
but also the problem is that they said that noone has did something on the eva

[Johan Guldmyr]

That error is probably related to a snapshot with dynamic allocation on a disk that has gotten full.

That is related to business copy.

[ilayy]

but the date of creation is 21-jan-2011
if i want to delete it from sssu can you provice me the correct command?

[Johan Guldmyr]

I think you should read the SSSU reference guide.

Also I cannot read from the screenshots of yours so I cannot give you the exact syntax.

[ilayy]

it seems like a snapshot so i delete it from the sssu

[Johan Guldmyr]

Did it work to delete it?

[ilayy]

yes johan i delete it from the sssu and it works because it seems from the error that appears on the log and that i have mentioned in this case that it is a snapshot but i didn't know how it was created automatically as all who has access to the system said that they didn't create it also it is impossible to be dynamic snapshot that transmitted to the overcomit state because there is no space on the disk group because the date of creation was too recent