Hello Wolfgang,
i know this has been solved at the customer site, nevertheless i want to post the solution as reference.
The log size of a diskgroup is determined by the smallest log size on any device that is member of the diskgroup. It does not matter whether that log is active or not. The log size itself is determined by the size of the private region.
To fix this problem in this specific case, you need to take all disks with a loglen of 197 out of the diskgroup, re-initialize the disks with a bigger private region and put them back in the diskgroup. This will lift the loglen of the diskgroup to the next smallest log, which is 883 blocks.
This solution was tested at the customer site. The customer was able to create a volume directly after taking out the last disk with 197 block log.
Regards,
Clemens Huebner
