Pinned topic Can I change extent size of V7000 under using the volumes.
Please teach me.
When I have read a referrence, I found the description "In the V7000, extent size can be able to change under the volumes ware used.".
(Of cause the volumes are existing in the storage pool I want to change extent size..)
Is it possible to change extent size under the situation?
(I have read the CLI manual chapter "chmdiskgrp", but no option about changing extent size.)
Re: Can I change extent size of V7000 under using the volumes.2011-02-07T14:57:43ZThis is the accepted answer. This is the accepted answer.Hi,
It is possible to change the extent size, but it's not a simple operation, and will require you having some spare storage to use.
The procedure is to use volume mirroring techniques to move the volume from the current storage pool into a new storage pool, and to set the new storage pool to use the extent size you are looking for.
I don't believe that the V7000 GUI currently lets you choose an extent size - it simply chooses the default of 256 MB. Therefore you would need to create the new storage pool using the command line interface (svctask mkmdiskgrp)
Hope this helps
Re: Can I change extent size of V7000 under using the volumes.2011-02-08T01:51:45ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
Arthruyoung 01000021N98 Posts
Re: Can I change extent size of V7000 under using the volumes.2013-06-12T15:15:57ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
when i want to use clone or backup method to do a vdisk copy.But i get a error message:
CMMVC5861E The action failed because there were
not enough extents on the managed disk
Explanation: The action failed because there were not
enough extents on the managed disk (MDisk)
so this message is mean svc extend size for this Mdisk is not enough ( my extend size is 256MB)?
or have others error config?
chriscanto 120000F8G2292 Posts
Re: Can I change extent size of V7000 under using the volumes.2013-06-12T15:56:28ZThis is the accepted answer. This is the accepted answer.
- Arthruyoung 01000021N9
That sounds like the sort of error you'd get if you didn't have enough free space in the destination storage pool where you're trying to create the new volume. Have you looked at the available capacity for the pool?
Mind you, as it's singular "mdisk", rather than "not enough extents in the managed disk group" then it sounds like you might be trying to create a copy on an image mode volume, or perhaps a sequential mdisk?
You might have to put this error in the context of your configuration and the specific CLI command being run if you need more help.