chore(v1): Closes DAR #449. Recommend against using LVM with Enterprise.

Closes https://github.com/influxdata/DAR/issues/449
Adds recommendation from @abalone23

content/enterprise_influxdb/v1/introduction/installation_requirements.md

@@ -31,11 +31,13 @@ The following are the most frequently overlooked requirements when installing a
 - [Synchronize time between hosts](#synchronize-time-between-hosts)
 - [Use SSDs](#use-ssds)
 - [Do not use NFS or NFS-based services](#do-not-use-nfs-or-nfs-based-services)
+- [Do not use LVM](#do-not-use-lvm)
 - [Disable swap](#disable-swap)
 - [Use three and only three meta nodes](#use-three-and-only-three-meta-nodes)
 - [Meta and data nodes are fully independent](#meta-and-data-nodes-are-fully-independent)
 - [Install Chronograf last](#install-chronograf-last)
 
+
 #### Ensure connectivity between machines
 
 All nodes in the cluster must be able to resolve each other by hostname or IP,
@@ -64,6 +66,13 @@ or services such as [AWS EFS](https://aws.amazon.com/efs/),
 [Google Filestore](https://cloud.google.com/filestore), or 
 [Azure files](https://azure.microsoft.com/en-us/services/storage/files/).
 
+#### Do not use LVM 
+
+Don't use LVM for software RAID, JBOD, or disk encryption.
+These use cases can lead to performance issues. 
+
+If you use LVM solely for creating logical volumes, use it with Device Mapper’s linear mapping for optimal performance.
+
 #### Disable swap
 
 To avoid potential disk contention when InfluxDB is under high load,