You don't see the same problem if you create a volume with the 'no init to rescue' option. In this case, the problem could relate with the writesame feature controller used while initialization. In controller system configuration menu, there have a feature called 'Write Same for Initialization', please disable this feature and recreate the volume to see if problem disappeared.