This bid is based on the following assumptions - please clarify if they are incorrect:
1. That you are currently directly using an LVM volume or a raw block device, and it is okay to keep that block device as is.
2. That you are either using external DRBD metadata, or you are using internal DRBD metadata and are happy for the DRBD metadata to remain at the end of the volume where it will take up a small amount of space but will not cause any harm.
My quote is to reconfigure the system so it will directly mount the DRBD backing device without going through DRBD, but does not include any work to resize the filesystem currently running on top of DRBD to allow it to make use of the extra space currently used for DRBD internal metadata (if applicable). A resize will sometimes be possible (depending on the filesystem), but I don't recommend doing the resize because the amount of disk space wasted is usually small, and resizing filesystems does not always work reliably, so it would require having another disk volume available for backing up all data on the disk.
This change will require a short downtime for any services that have files open / mapped on the DRDB volume, while the DRDB disk is unmounted and the backing device is mounted directly.