Basic changes.

Author: roygara

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/06/2023
 ms.author: rogarana
 ms.subservice: disks
 ms.collection: linux
@@ -103,7 +103,7 @@ 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.
 
@@ -153,12 +153,12 @@ 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:
+Next, open the **/etc/fstab** file in a text editor as follows:
 
 ```bash
-sudo nano /etc/fstab
+sudo vi /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:
@@ -167,7 +167,7 @@ In this example, use the UUID value for the `/dev/sdc1` device that was created
 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.
+We used the vi editor, so when you are done editing the file, press `Esc` to enter command mode and `wq` to 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 +200,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:
 
@@ -225,6 +225,12 @@ There are two ways to enable TRIM support in your Linux VM. As usual, consult yo
     sudo fstrim /datadrive
     ```
 
+    **SLSE**
+    
+    ```bash
+    sudo fstrim /datadrive
+    ```
+
 ## Next steps
 
 For more information, and to help troubleshoot disk issues, see [Troubleshoot Linux VM device name changes](/troubleshoot/azure/virtual-machines/troubleshoot-device-names-problems).

articles/virtual-machines/linux/expand-disks.md

@@ -5,7 +5,7 @@ author: pagienge
 ms.service: storage
 ms.collection: linux
 ms.topic: how-to
-ms.date: 12/09/2022
+ms.date: 01/06/2023
 ms.author: pagienge
 ms.subservice: disks
 ms.custom: references_regions, ignite-fall-2021, devx-track-azurecli 
@@ -202,7 +202,7 @@ tmpfs          tmpfs      65M     0   65M   0% /run/user/1000
 user@ubuntu:~#
 ```
 
-# [SuSE](#tab/suse)
+# [SUSE](#tab/suse)
 
 To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15, and SUSE SLES 15 for SAP:
 
@@ -211,13 +211,13 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Access your VM as the **root** user by using the ```sudo``` command after logging in as another user:
 
    ```
-   linux:~ # sudo -i
+   sudo -i
    ```
 
 1. Use the following command to install the **growpart** package, which will be used to resize the partition, if it is not already present:
 
    ```
-   linux:~ # zypper install growpart
+   zypper install growpart
    ```
 
 1. Use the `lsblk` command to find the partition mounted on the root of the file system (**/**). In this case, we see that partition 4 of device **sda** is mounted on **/**:
@@ -237,7 +237,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Resize the required partition by using the `growpart` command and the partition number determined in the preceding step:
 
    ```
-   linux:~ # growpart /dev/sda 4
+   growpart /dev/sda 4
    CHANGED: partition=4 start=3151872 old: size=59762655 end=62914527 new: size=97511391 end=100663263
    ```
 
@@ -246,7 +246,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
    The following output shows that the **/dev/sda4** partition has been resized to 46.5 GB:
    
    ```
-   linux:~ # lsblk
+   lsblk
    NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    sda      8:0    0   48G  0 disk
    ├─sda1   8:1    0    2M  0 part
@@ -260,7 +260,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Identify the type of file system on the OS disk by using the `lsblk` command with the `-f` flag:
 
    ```
-   linux:~ # lsblk -f
+   lsblk -f
    NAME   FSTYPE LABEL UUID                                 MOUNTPOINT
    sda
    ├─sda1
@@ -282,7 +282,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
    Example output:
    
    ```
-   linux:~ # xfs_growfs /
+   xfs_growfs /
    meta-data=/dev/sda4              isize=512    agcount=4, agsize=1867583 blks
             =                       sectsz=512   attr=2, projid32bit=1
             =                       crc=1        finobt=0 spinodes=0 rmapbt=0
@@ -299,19 +299,19 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
    For **ext4**, use this command:
    
    ```
-   linux:~ #resize2fs /dev/sda4
+   resize2fs /dev/sda4
    ```
    
 1. Verify the increased file system size for **df -Th** by using this command:
    
    ```
-   linux:~ #df -Thl
+   df -Thl
    ```
    
    Example output:
    
    ```
-   linux:~ # df -Thl
+   df -Thl
    Filesystem     Type      Size  Used Avail Use% Mounted on
    devtmpfs       devtmpfs  445M  4.0K  445M   1% /dev
    tmpfs          tmpfs     458M     0  458M   0% /dev/shm
@@ -334,13 +334,13 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Access your VM as the **root** user by using the ```sudo``` command after logging in as another user:
 
    ```bash
-   [root@rhel-lvm ~]# sudo -i
+   sudo -i
    ```
 
 1. Use the `lsblk` command to determine which logical volume (LV) is mounted on the root of the file system (**/**). In this case, we see that **rootvg-rootlv** is mounted on **/**. If a different filesystem is in need of resizing, substitute the LV and mount point throughout this section.
 
    ```shell
-   [root@rhel-lvm ~]# lsblk -f
+   lsblk -f
    NAME                  FSTYPE      LABEL   UUID                                   MOUNTPOINT
    fd0
    sda
@@ -359,7 +359,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Check whether there is free space in the LVM volume group (VG) containing the root partition.  If there is free space, skip to step 12.
 
    ```bash
-   [root@rhel-lvm ~]# vgdisplay rootvg
+   vgdisplay rootvg
    --- Volume group ---
    VG Name               rootvg
    System ID
@@ -387,20 +387,20 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Install the **cloud-utils-growpart** package to provide the **growpart** command, which is required to increase the size of the OS disk and the gdisk handler for GPT disk layouts  This package is preinstalled on most marketplace images
 
    ```bash
-   [root@rhel-lvm ~]# yum install cloud-utils-growpart gdisk
+   yum install cloud-utils-growpart gdisk
    ```
 
 1. Determine which disk and partition holds the LVM physical volume (PV) or volumes in the volume group named **rootvg** by using the **pvscan** command. Note the size and free space listed between the brackets (**[** and **]**).
 
    ```bash
-   [root@rhel-lvm ~]# pvscan
+   pvscan
    PV /dev/sda4   VG rootvg          lvm2 [<63.02 GiB / <38.02 GiB free]
    ```
 
 1. Verify the size of the partition by using `lsblk`.
 
    ```bash
-   [root@rhel-lvm ~]# lsblk /dev/sda4
+   lsblk /dev/sda4
    NAME            MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda4              8:4    0  63G  0 part
    ├─rootvg-tmplv  253:1    0   2G  0 lvm  /tmp
@@ -414,14 +414,14 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Expand the partition containing this PV using *growpart*, the device name, and partition number. Doing so will expand the specified partition to use all the free contiguous space on the device.
 
    ```bash
-   [root@rhel-lvm ~]# growpart /dev/sda 4
+   growpart /dev/sda 4
    CHANGED: partition=4 start=2054144 old: size=132161536 end=134215680 new: size=199272414 end=201326558
    ```
 
 1. Verify that the partition has resized to the expected size by using the `lsblk` command again. Notice that in the example **sda4** has changed from 63G to 95G.
 
    ```bash
-   [root@rhel-lvm ~]# lsblk /dev/sda4
+   lsblk /dev/sda4
    NAME            MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda4              8:4    0  95G  0 part
    ├─rootvg-tmplv  253:1    0   2G  0 lvm  /tmp
@@ -435,28 +435,28 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Expand the PV to use the rest of the newly expanded partition
 
    ```bash
-   [root@rhel-lvm ~]# pvresize /dev/sda4
+   pvresize /dev/sda4
    Physical volume "/dev/sda4" changed
    1 physical volume(s) resized or updated / 0 physical volume(s) not resized
    ```
 
 1. Verify the new size of the PV is the expected size, comparing to original **[size / free]** values.
 
    ```bash
-   [root@rhel-lvm ~]# pvscan
+   pvscan
    PV /dev/sda4   VG rootvg          lvm2 [<95.02 GiB / <70.02 GiB free]
    ```
 
 1. Expand the LV by the required amount, which does not need to be all the free space in the volume group.  In the following example, **/dev/mapper/rootvg-rootlv** is resized from 2 GB to 12 GB (an increase of 10 GB) through the following command. This command will also resize the file system on the LV.
 
    ```bash
-   [root@rhel-lvm ~]# lvresize -r -L +10G /dev/mapper/rootvg-rootlv
+   lvresize -r -L +10G /dev/mapper/rootvg-rootlv
    ```
 
    Example output:
 
    ```bash
-   [root@rhel-lvm ~]# lvresize -r -L +10G /dev/mapper/rootvg-rootlv
+   lvresize -r -L +10G /dev/mapper/rootvg-rootlv
    Size of logical volume rootvg/rootlv changed from 2.00 GiB (512 extents) to 12.00 GiB (3072 extents).
    Logical volume rootvg/rootlv successfully resized.
    meta-data=/dev/mapper/rootvg-rootlv isize=512    agcount=4, agsize=131072 blks
@@ -476,10 +476,9 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
    Example output:
 
    ```shell
-   [root@rhel-lvm ~]# df -Th /
+   df -Th /
    Filesystem                Type  Size  Used Avail Use% Mounted on
    /dev/mapper/rootvg-rootlv xfs    12G   71M   12G   1% /
-   [root@rhel-lvm ~]#
    ```
 
 > [!NOTE]
@@ -492,21 +491,21 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Access your VM as the **root** user by using the ```sudo``` command after logging in as another user:
 
    ```bash
-   [root@rhel-raw ~]# sudo -i
+   sudo -i
    ```
 
 1. When the VM has restarted, perform the following steps:
 
    1. Install the **cloud-utils-growpart** package to provide the **growpart** command, which is required to increase the size of the OS disk and the gdisk handler for GPT disk layouts. This package is preinstalled on most marketplace images
 
    ```bash
-   [root@rhel-raw ~]# yum install cloud-utils-growpart gdisk
+   yum install cloud-utils-growpart gdisk
    ```
 
 1. Use the **lsblk -f** command to verify the partition and filesystem type holding the root (**/**) partition
 
    ```bash
-   [root@rhel-raw ~]# lsblk -f
+   lsblk -f
    NAME    FSTYPE LABEL UUID                                 MOUNTPOINT
    sda
    ├─sda1  xfs          2a7bb59d-6a71-4841-a3c6-cba23413a5d2 /boot
@@ -520,7 +519,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. For verification, start by listing the partition table of the sda disk with **gdisk**.  In this example, we see a 48.0 GiB disk with partition #2 sized 29.0 GiB.  The disk was expanded from 30 GB to 48 GB in the Azure portal.
 
    ```bash
-   [root@rhel-raw ~]# gdisk -l /dev/sda
+   gdisk -l /dev/sda
    GPT fdisk (gdisk) version 0.8.10
 
    Partition table scan:
@@ -548,14 +547,14 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Expand the partition for root, in this case sda2 by using the **growpart** command.  Using this command expands the partition to use all of the contiguous space on the disk.
 
    ```bash
-   [root@rhel-raw ~]# growpart /dev/sda 2
+   growpart /dev/sda 2
    CHANGED: partition=2 start=2050048 old: size=60862464 end=62912512 new: size=98613214 end=100663262
    ```
 
 1. Now print the new partition table with **gdisk** again.  Notice that partition 2 has is now sized 47.0 GiB
 
    ```bash
-   [root@rhel-raw ~]# gdisk -l /dev/sda
+   gdisk -l /dev/sda
    GPT fdisk (gdisk) version 0.8.10
 
    Partition table scan:
@@ -583,7 +582,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Expand the filesystem on the partition with **xfs_growfs**, which is appropriate for a standard marketplace-generated RedHat system:
 
    ```bash
-   [root@rhel-raw ~]# xfs_growfs /
+   xfs_growfs /
    meta-data=/dev/sda2              isize=512    agcount=4, agsize=1901952 blks
             =                       sectsz=4096  attr=2, projid32bit=1
             =                       crc=1        finobt=0 spinodes=0
@@ -599,7 +598,7 @@ To increase the OS disk size in SUSE 12 SP4, SUSE SLES 12 for SAP, SUSE SLES 15,
 1. Verify the new size is reflected with the **df** command
 
    ```bash
-   [root@rhel-raw ~]# df -hl
+   df -hl
    Filesystem      Size  Used Avail Use% Mounted on
    devtmpfs        452M     0  452M   0% /dev
    tmpfs           464M     0  464M   0% /dev/shm