Merge pull request #223223 from roygara/linFirst

Initial draft changes

Author: jborsecnik

articles/virtual-machines/linux/add-disk.md

@@ -6,7 +6,7 @@ ms.service: storage
 ms.subservice: disks
 ms.collection: linux
 ms.topic: how-to
-ms.date: 12/08/2022
+ms.date: 01/09/2023
 ms.author: rogarana
 ---
 
@@ -55,7 +55,7 @@ ssh [email protected]
 
 ### Find the disk
 
-Once connected to your VM, you need to find the disk. In this example, we are using `lsblk` to list the disks. 
+Once you connect to your VM, find the disk. In this example, we're using `lsblk` to list the disks. 
 
 ```bash
 lsblk -o NAME,HCTL,SIZE,MOUNTPOINT | grep -i "sd"
@@ -73,19 +73,19 @@ sdb     1:0:1:0      14G
 sdc     3:0:0:0      50G
 ```
 
-Here, `sdc` is the disk that we want, because it is 50G. If you add multiple disks, and aren't sure which disk it is based on size alone, you can go to the VM page in the portal, select **Disks**, and check the LUN number for the disk under **Data disks**. Compare the LUN number from the portal to the last number of the **HTCL** portion of the output, which is the LUN.
+Here, `sdc` is the disk that we want, because it's 50G. If you add multiple disks, and aren't sure which disk it's based on size alone, you can go to the VM page in the portal, select **Disks**, and check the LUN number for the disk under **Data disks**. Compare the LUN number from the portal to the last number of the **HTCL** portion of the output, which is the LUN.
 
 
 ### Format the disk
 
-Format the disk with `parted`, if the disk size is 2 tebibytes (TiB) or larger then you must use GPT partitioning, if it is under 2TiB, then you can use either MBR or GPT partitioning. 
+Format the disk with `parted`, if the disk size is two tebibytes (TiB) or larger then you must use GPT partitioning, if it is under 2TiB, then you can use either MBR or GPT partitioning. 
 
 > [!NOTE]
 > It is recommended that you use the latest version `parted` that is available for your distro.
 > If the disk size is 2 tebibytes (TiB) or larger, you must use GPT partitioning. If disk size is under 2 TiB, then you can use either MBR or GPT partitioning.  
 
 
-The following example uses `parted` on `/dev/sdc`, which is where the first data disk will typically be on most VMs. Replace `sdc` with the correct option for your disk. We are also formatting it using the [XFS](https://xfs.wiki.kernel.org/) filesystem.
+The following example uses `parted` on `/dev/sdc`, which is where the first data disk will typically be on most VMs. Replace `sdc` with the correct option for your disk. We're also formatting it using the [XFS](https://xfs.wiki.kernel.org/) filesystem.
 
 ```bash
 sudo parted /dev/sdc --script mklabel gpt mkpart xfspart xfs 0% 100%
@@ -112,7 +112,7 @@ sudo mount /dev/sdc1 /datadrive
 
 ### Persist the mount
 
-To ensure that the drive is remounted automatically after a reboot, it must be added to the */etc/fstab* file. It is also highly recommended that the UUID (Universally Unique Identifier) is used in */etc/fstab* to refer to the drive rather than just the device name (such as, */dev/sdc1*). If the OS detects a disk error during boot, using the UUID avoids the incorrect disk being mounted to a given location. Remaining data disks would then be assigned those same device IDs. To find the UUID of the new drive, use the `blkid` utility:
+To ensure that the drive is remounted automatically after a reboot, it must be added to the */etc/fstab* file. It's also highly recommended that the UUID (Universally Unique Identifier) is used in */etc/fstab* to refer to the drive rather than just the device name (such as, */dev/sdc1*). If the OS detects a disk error during boot, using the UUID avoids the incorrect disk being mounted to a given location. Remaining data disks would then be assigned those same device IDs. To find the UUID of the new drive, use the `blkid` utility:
 
 ```bash
 sudo blkid
@@ -131,19 +131,13 @@ The output looks similar to the following example:
 > [!NOTE]
 > Improperly editing the **/etc/fstab** file could result in an unbootable system. If unsure, refer to the distribution's documentation for information on how to properly edit this file. It is also recommended that a backup of the /etc/fstab file is created before editing.
 
-Next, open the */etc/fstab* file in a text editor as follows:
-
-```bash
-sudo nano /etc/fstab
-```
-
-In this example, use the UUID value for the `/dev/sdc1` device that was created in the previous steps, and the mountpoint of `/datadrive`. Add the following line to the end of the `/etc/fstab` file:
+Next, open the **/etc/fstab** file in a text editor. Add a line to the end of the file, using the UUID value for the `/dev/sdc1` device that was created in the previous steps, and the mountpoint of `/datadrive`. Using the example from this article, the new line would look like the following:
 
 ```bash
 UUID=33333333-3b3b-3c3c-3d3d-3e3e3e3e3e3e   /datadrive   xfs   defaults,nofail   1   2
 ```
 
-In this example, we are using the nano editor, so when you are done editing the file, use `Ctrl+O` to write the file and `Ctrl+X` to exit the editor.
+When you're done editing the file, save and close the editor.
 
 > [!NOTE]
 > Later removing a data disk without editing fstab could cause the VM to fail to boot. Most distributions provide either the *nofail* and/or *nobootwait* fstab options. These options allow a system to boot even if the disk fails to mount at boot time. Consult your distribution's documentation for more information on these parameters.
@@ -166,19 +160,26 @@ There are two ways to enable TRIM support in your Linux VM. As usual, consult yo
 
 - In some cases, the `discard` option may have performance implications. Alternatively, you can run the `fstrim` command manually from the command line, or add it to your crontab to run regularly:
 
-    **Ubuntu**
+# [Ubuntu](#tab/ubuntu)
 
-    ```bash
-    sudo apt-get install util-linux
-    sudo fstrim /datadrive
-    ```
+```bash
+sudo apt-get install util-linux
+sudo fstrim /datadrive
+```
 
-    **RHEL/CentOS**
+# [RHEL](#tab/rhel)
 
-    ```bash
-    sudo yum install util-linux
-    sudo fstrim /datadrive
-    ```
+```bash
+sudo yum install util-linux
+sudo fstrim /datadrive
+```
+
+# [SUSE](#tab/suse)
+
+```bash
+sudo fstrim /datadrive
+```
+---
 
 ## Troubleshooting
 
@@ -187,4 +188,4 @@ There are two ways to enable TRIM support in your Linux VM. As usual, consult yo
 ## Next steps
 
 * To ensure your Linux VM is configured correctly, review the [Optimize your Linux machine performance](/previous-versions/azure/virtual-machines/linux/optimization) recommendations.
-* Expand your storage capacity by adding additional disks and [configure RAID](/previous-versions/azure/virtual-machines/linux/configure-raid) for additional performance.
+* Expand your storage capacity by adding more disks and [configure RAID](/previous-versions/azure/virtual-machines/linux/configure-raid) for extra performance.

articles/virtual-machines/linux/attach-disk-portal.md

@@ -4,7 +4,7 @@ description: Use the portal to attach new or existing data disk to a Linux VM.
 author: roygara
 ms.service: storage
 ms.topic: how-to
-ms.date: 08/13/2021
+ms.date: 01/09/2023
 ms.author: rogarana
 ms.subservice: disks
 ms.collection: linux
@@ -38,14 +38,14 @@ Before you attach disks to your VM, review these tips:
    :::image type="content" source="./media/attach-disk-portal/create-new-md.png" alt-text="Review disk settings.":::
 
 
-1. When you are done, select **Save** at the top of the page to create the managed disk and update the VM configuration.
+1. When you're done, select **Save** at the top of the page to create the managed disk and update the VM configuration.
 
 
 ## Attach an existing disk
 1. On the **Disks** pane, under **Data disks**, select  **Attach existing disks**.
-1. Click the drop-down menu for **Disk name** and select a disk from the list of available managed disks. 
+1. Select the drop-down menu for **Disk name** and select a disk from the list of available managed disks. 
 
-1. Click **Save** to attach the existing managed disk and update the VM configuration:
+1. Select **Save** to attach the existing managed disk and update the VM configuration:
 
 
 ## Connect to the Linux VM to mount the new disk
@@ -57,7 +57,7 @@ ssh [email protected]
 
 ## Find the disk
 
-Once connected to your VM, you need to find the disk. In this example, we are using `lsblk` to list the disks. 
+Once connected to your VM, you need to find the disk. In this example, we're using `lsblk` to list the disks. 
 
 ```bash
 lsblk -o NAME,HCTL,SIZE,MOUNTPOINT | grep -i "sd"
@@ -75,15 +75,15 @@ sdb     1:0:1:0      14G
 sdc     3:0:0:0       4G
 ```
 
-In this example, the disk that I added is `sdc`. It is a LUN 0 and is 4GB.
+In this example, the disk that was added was `sdc`. It's a LUN 0 and is 4GB.
 
-For a more complex example, here is what multiple data disks look like in the portal:
+For a more complex example, here's what multiple data disks look like in the portal:
 
 :::image type="content" source="./media/attach-disk-portal/find-disk.png" alt-text="Screenshot of multiple disks shown in the portal.":::
 
 In the image, you can see that there are 3 data disks: 4 GB on LUN 0, 16GB at LUN 1, and 32G at LUN 2.
 
-Here is what that might look like using `lsblk`:
+Here's what that might look like using `lsblk`:
 
 ```bash
 sda     0:0:0:0      30G
@@ -103,16 +103,16 @@ From the output of `lsblk` you can see that the 4GB disk at LUN 0 is `sdc`, the
 
 > [!IMPORTANT]
 > If you are using an existing disk that contains data, skip to [mounting the disk](#mount-the-disk). 
-> The following instuctions will delete data on the disk.
+> The following instructions will delete data on the disk.
 
-If you are attaching a new disk, you need to partition the disk.
+If you're attaching a new disk, you need to partition the disk.
 
 The `parted` utility can be used to partition and to format a data disk.
-- It is recommended that you use the latest version `parted` that is available for your distro.
+- Use the latest version `parted` that is available for your distro.
 - If the disk size is 2 tebibytes (TiB) or larger, you must use GPT partitioning. If disk size is under 2 TiB, then you can use either MBR or GPT partitioning.  
 
 
-The following example uses `parted` on `/dev/sdc`, which is where the first data disk will typically be on most VMs. Replace `sdc` with the correct option for your disk. We are also formatting it using the [XFS](https://xfs.wiki.kernel.org/) filesystem.
+The following example uses `parted` on `/dev/sdc`, which is where the first data disk will typically be on most VMs. Replace `sdc` with the correct option for your disk. We're also formatting it using the [XFS](https://xfs.wiki.kernel.org/) filesystem.
 
 ```bash
 sudo parted /dev/sdc --script mklabel gpt mkpart xfspart xfs 0% 100%
@@ -136,7 +136,7 @@ Use `mount` to then mount the filesystem. The following example mounts the */dev
 sudo mount /dev/sdc1 /datadrive
 ```
 
-To ensure that the drive is remounted automatically after a reboot, it must be added to the */etc/fstab* file. It is also highly recommended that the UUID (Universally Unique Identifier) is used in */etc/fstab* to refer to the drive rather than just the device name (such as, */dev/sdc1*). If the OS detects a disk error during boot, using the UUID avoids the incorrect disk being mounted to a given location. Remaining data disks would then be assigned those same device IDs. To find the UUID of the new drive, use the `blkid` utility:
+To ensure that the drive is remounted automatically after a reboot, it must be added to the */etc/fstab* file. It's also highly recommended that the UUID (Universally Unique Identifier) is used in */etc/fstab* to refer to the drive rather than just the device name (such as, */dev/sdc1*). If the OS detects a disk error during boot, using the UUID avoids the incorrect disk being mounted to a given location. Remaining data disks would then be assigned those same device IDs. To find the UUID of the new drive, use the `blkid` utility:
 
 ```bash
 sudo blkid
@@ -153,21 +153,15 @@ The output looks similar to the following example:
 ```
 
 > [!NOTE]
-> Improperly editing the **/etc/fstab** file could result in an unbootable system. If unsure, refer to the distribution's documentation for information on how to properly edit this file. It is also recommended that a backup of the /etc/fstab file is created before editing.
+> Improperly editing the **/etc/fstab** file could result in an unbootable system. If unsure, refer to the distribution's documentation for information on how to properly edit this file. You should create a backup of the **/etc/fstab** file is created before editing.
 
-Next, open the */etc/fstab* file in a text editor as follows:
-
-```bash
-sudo nano /etc/fstab
-```
-
-In this example, use the UUID value for the `/dev/sdc1` device that was created in the previous steps, and the mountpoint of `/datadrive`. Add the following line to the end of the `/etc/fstab` file:
+Next, open the **/etc/fstab** file in a text editor. Add a line to the end of the file, using the UUID value for the `/dev/sdc1` device that was created in the previous steps, and the mountpoint of `/datadrive`. Using the example from this article, the new line would look like the following:
 
 ```bash
 UUID=33333333-3b3b-3c3c-3d3d-3e3e3e3e3e3e   /datadrive   xfs   defaults,nofail   1   2
 ```
 
-We used the nano editor, so when you are done editing the file, use `Ctrl+O` to write the file and `Ctrl+X` to exit the editor.
+When you're done editing the file, save and close the editor.
 
 > [!NOTE]
 > Later removing a data disk without editing fstab could cause the VM to fail to boot. Most distributions provide either the *nofail* and/or *nobootwait* fstab options. These options allow a system to boot even if the disk fails to mount at boot time. Consult your distribution's documentation for more information on these parameters.
@@ -200,7 +194,7 @@ You can see that `sdc` is now mounted at `/datadrive`.
 
 ### TRIM/UNMAP support for Linux in Azure
 
-Some Linux kernels support TRIM/UNMAP operations to discard unused blocks on the disk. This feature is primarily useful in standard storage to inform Azure that deleted pages are no longer valid and can be discarded, and can save money if you create large files and then delete them.
+Some Linux kernels support TRIM/UNMAP operations to discard unused blocks on the disk. This feature is primarily useful to inform Azure that deleted pages are no longer valid and can be discarded. This feature can save money on disks that are billed based on the amount of consumed storage, such as unmanaged standard disks and disk snapshots.
 
 There are two ways to enable TRIM support in your Linux VM. As usual, consult your distribution for the recommended approach:
 
@@ -211,19 +205,26 @@ There are two ways to enable TRIM support in your Linux VM. As usual, consult yo
     ```
 * In some cases, the `discard` option may have performance implications. Alternatively, you can run the `fstrim` command manually from the command line, or add it to your crontab to run regularly:
 
-    **Ubuntu**
-  
-    ```bash
-    sudo apt-get install util-linux
-    sudo fstrim /datadrive
-    ```
-  
-    **RHEL/CentOS**
+# [Ubuntu](#tab/ubuntu)
 
-    ```bash
-    sudo yum install util-linux
-    sudo fstrim /datadrive
-    ```
+```bash
+sudo apt-get install util-linux
+sudo fstrim /datadrive
+```
+
+# [RHEL](#tab/rhel)
+
+```bash
+sudo yum install util-linux
+sudo fstrim /datadrive
+```
+
+# [SUSE](#tab/suse)
+
+```bash
+sudo fstrim /datadrive
+```
+---
 
 ## Next steps
 

articles/virtual-machines/linux/detach-disk.md

@@ -5,7 +5,7 @@ author: roygara
 ms.service: storage
 ms.collection: linux
 ms.topic: how-to
-ms.date: 06/08/2022
+ms.date: 01/09/2023
 ms.author: rogarana
 ms.subservice: disks 
 ms.custom: devx-track-azurecli
@@ -69,19 +69,15 @@ Edit the */etc/fstab* file to remove references to the disk.
 > [!NOTE]
 > Improperly editing the **/etc/fstab** file could result in an unbootable system. If unsure, refer to the distribution's documentation for information on how to properly edit this file. It is also recommended that a backup of the /etc/fstab file is created before editing.
 
-Open the */etc/fstab* file in a text editor as follows:
-
-```bash
-sudo vi /etc/fstab
-```
-
-In this example, the following line needs to be deleted from the */etc/fstab* file:
+Open the **/etc/fstab** file in a text editor and remove the line containing the UUID of your disk. Using the example values in this article, the line would look like the following:
 
 ```bash
 UUID=33333333-3b3b-3c3c-3d3d-3e3e3e3e3e3e   /datadrive   ext4   defaults,nofail   1   2
 ```
 
-Use `umount` to unmount the disk. The following example unmounts the */dev/sdc1* partition from the */datadrive* mount point:
+Save and close the file when you're done.
+
+Next, use `umount` to unmount the disk. The following example unmounts the */dev/sdc1* partition from the */datadrive* mount point:
 
 ```bash
 sudo umount /dev/sdc1 /datadrive