On Exadata systems, ASM disk group configurations require that:
Grid Disks Must Have Similar Performance Characteristics: Within a disk group, grid disks must not only be of the same size but also need to exhibit similar performance traits. This consistency ensures balanced I/O operations and optimizes the performance for ASM mirroring and striping across disks.
Sparse Diskgroups: These are specialized virtual objects that reside within the DATA disk group. Sparse diskgroups are used to support snapshots and other space-efficient storage solutions by creating virtual representations of grid disks within an existing disk group without consuming additional physical space.
These characteristics are fundamental to ensuring that ASM maintains optimal performance and storage efficiency on Exadata platforms.

According to Oracle documentation12, patchmgr is the utility used to update software for Exadata infrastructure components. It can apply patches in a rolling or non-rolling manner depending on the argument and input file provided.

In an Automatic Storage Management (ASM) environment, failure groups are used to provide redundancy for the storage disks. Failure groups are used to group together a set of disks and ensure that no two copies of the same data are stored on the same physical disk or storage server. This way, if a disk or storage server fails, the data can still be accessed from the other copy.
For example, if the disks in a failure group are mirrored, one copy of the data is stored on one set of disks, and the other copy is stored on another set of disks. This way, if a disk or storage server fails, the data can still be accessed from the other copy.
ASM failure groups also provide the option to spread the data across different storage servers, this way, even if a storage server fails, data can still be accessed from the other storage servers in the group. This will improve the availability of the data.

After running the commands above, the filesystem mounted on /u01 is on the logical volume /dev/mapper/VGExaDb-LVDbOral. So, to add 20G of space to the filesystem mounted on /u01, the command that needs to be run is:
lvextend -L +20G --verbose /dev/mapper/VGExaDb-LVDbOral
This command will extend the logical volume /dev/mapper/VGExaDb-LVDbOral by 20 GB of space. It is important to note that the option --verbose is used to display the progress of the operation.

Oracle Exadata Deployment Assistant (OEDA) enables customers to deploy Oracle Exadata Database Machine in virtualized environments and it support both bare metal and virtual machine deployment in an Exadata X9M Quarter Rack.