What happens if you bring a disk in an Exadata Storage Server back online before the disk_repair_time expires?

What happens if you bring a disk in an Exadata Storage Server back online before the
disk_repair_time expires?

A.
You only have to drop and add the disk.

B.
You have to drop and add the disk and then rebalance data onto it.

C.
Nothing.

D.
Fast resync on the disk happens automatically.

Explanation:
In the 11g scenario with fast mirror resync,the time which is needed to
resynchronize a failure is reduced dramatically if the failure is only a transient failure and can be
fixed within disk_repair_time. Only those extents which have been marked as modified in between
need to be rebalanced after the failed disk has re-joined the disk group.
The DISK_REPAIR_TIME disk group attribute specifies how long a disk remains offline before
ASM drops the disk. If a disk is made available before the DISK_REPAIR_TIME parameter has
expired, the storage administrator can issue the ONLINE DISK command and ASM
resynchronizes the stale data from the mirror side. In Oracle Database 11g, the online disk
operation does not restart if there is a failure of the instance on which the disk is running. You
must reissue the command manually to bring the disk online.
Note:
The DISK_REPAIR_TIME attribute is used to define the time in which any transient failure (loose
cable connections or disk failures, etc.) should be rectified and the ASM disk can be brought back
online. The value of this attribute can be altered by using the ALTER DISKGROUP command.
Once the disk is repaired, the ALTER DISKGROUP ONLINE statement is issued to bring the disk

back online. The default value of the DISK_REPAIR_TIME attribute is 3.6 hours.
http://www.dba-oracle.com/t_11g_new_asm_fast_mirror.htm