[SERVER-41393] Drives don't come back up on Enterprise Amazon Linux during powercycle testing Created: 30/May/19  Updated: 29/Oct/23  Resolved: 03/Jun/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.2.0-rc0, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: tig-powercycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: STM 2019-06-17
Participants:
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.



 Comments   
Comment by Githook User [ 07/Jun/19 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}

Message: SERVER-41393 Fix specifying "shell: bash" for fuzzer functions.
Branch: master
https://github.com/mongodb/mongo/commit/4351145ceb3ec61f122e5e6a389e9b63d653528c

Edit: This commit was meant to say SERVER-41423.

Comment by Githook User [ 03/Jun/19 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-41393 Identify devices by their UUID in /etc/fstab.

This ensures they are automatically mounted following a machine reboot.

(cherry picked from commit 79091ef290d1c0d73f663787c7982cc4fef2959e)
Branch: v4.2
https://github.com/mongodb/mongo/commit/c710c8429d0c1dde5324d7fdbe2c5e1485bd8450

Comment by Githook User [ 03/Jun/19 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-41393 Identify devices by their UUID in /etc/fstab.

This ensures they are automatically mounted following a machine reboot.
Branch: master
https://github.com/mongodb/mongo/commit/79091ef290d1c0d73f663787c7982cc4fef2959e

Comment by Githook User [ 31/May/19 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-41393 Fix specifying "shell: bash" for fuzzer functions.
Branch: master
https://github.com/mongodb/mongo/commit/4351145ceb3ec61f122e5e6a389e9b63d653528c

Edit: This commit was meant to say SERVER-41423.

Generated at Thu Feb 08 04:57:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.