Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-41393

Drives don't come back up on Enterprise Amazon Linux during powercycle testing

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      STM 2019-06-17
    • Linked BF Score:
      50
    • Story Points:
      2

      Description

      Through experimentation with Brian McCarthy, we've found that EBS volumes only come back up with the amazon1-2018-test Evergreen distro if the entry in /etc/fstab uses the UUID of the drive. The ubuntu1604-powercycle Evergreen distro doesn't appear to be impacted. Note that this is also the recommendation in Amazon's documentation as well:

      To mount an attached EBS volume on every system reboot, add an entry for the device to the /etc/fstab file.

      You can use the device name, such as /dev/xvdf, in /etc/fstab, but we recommend using the device's 128-bit universally unique identifier (UUID) instead. Device names can change, but the UUID persists throughout the life of the partition. By using the UUID, you reduce the chances that the system becomes unbootable after a hardware reconfiguration. For more information, see Identifying the EBS Device.

      https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html#ebs-mount-after-reboot

      Based on https://unix.stackexchange.com/a/270216, we can use either the blkid -o value -s UUID /dev/xvd... or lsblk -no UUID /dev/xvd... command to get the UUID and write that in place of $device_name in the mount_drives.sh script.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: