Persistent disk identifiers

339 views
Skip to first unread message

Mark Woodbridge

unread,
Jul 13, 2016, 7:02:05 AM7/13/16
to gce-discussion
We mount all our additional persistent disks in `/etc/fstab` using `/dev/disk/by-id/google-[DISK_NAME]`, as recommended on this page https://cloud.google.com/compute/docs/disks/add-persistent-disk.

However, having just rebooted our server, all these symlinks have changed to `/dev/disk/by-id/scsi-0Google_PersistentDisk_[DISK_NAME]`. This obviously prevents them from being mounted - which is a big problem. Is this to be expected, or documented anywhere? We're on CentOS 6.

George (Google Cloud Support)

unread,
Jul 13, 2016, 4:59:53 PM7/13/16
to gce-discussion
Hello Mark,

I wasn't able to reproduce using the CentOS 6 image x86_64 built on 2016-07-11. The disk survived a reboot and I was able to access the mounted location and the df -h is showing the mounted disk.

Is it possible to provide me with the image build that you are using? Did you try using the latest image build?

Looking forward to your reply.

Sincerely,
George

Paul Nash

unread,
Jul 13, 2016, 8:15:39 PM7/13/16
to George (Google Cloud Support), gce-discussion
Hi Mark,

I checked with our guest OS engineering team, and they said that mounting the volumes by UUID should get you around issues like this. I'm not totally familiar with the procedure myself, but there are many references.

--
© 2016 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussio...@googlegroups.com.
To post to this group, send email to gce-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/b074904c-3cea-49a2-9976-1c1332c23db9%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Paul R. Nash | Product Manager, Compute Engine | paul...@google.com | 206-876-1620

Mark Woodbridge

unread,
Jul 14, 2016, 3:47:15 AM7/14/16
to gce-discussion
Thanks George. These machines were provisioned about 2 months ago using the public CentOS 6 and 7 images.

I can confirm that the /dev/disk/by-id/google-[DISK_NAME] symlinks are missing on all the machine that I have rebooted, and have not returned following subsequent reboots, or when attaching new disks. I'm aware of the workarounds (such as mounting using UUID, or by the scsi-0Google_PersistentDisk symlinks), but the obvious concern is that having following the instructions for attaching persistent disks we were left with machines that failed to boot due to the missing symlinks.

Mark.

Paul Nash

unread,
Jul 19, 2016, 2:02:27 AM7/19/16
to Mark Woodbridge, gce-discussion
Hi Mark,

FYI we've been having an ongoing discussion about this in the engineering team, and hope to determine the cause of the unexpected change, above and beyond the workarounds we mentioned. Someone may reach out to you directly if we need to get more information about this issue. Sorry that it happened, and thanks for reporting it here.

Thx,
-P

--
© 2016 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussio...@googlegroups.com.
To post to this group, send email to gce-dis...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Mark Woodbridge

unread,
Jul 19, 2016, 3:27:43 AM7/19/16
to Paul Nash, gce-discussion
Thanks Paul. Last night's updates have resolved the issue.

Mark.
--
Mark Woodbridge
Co-founder & CTO
Chaser
www.chaser.io
twitter.com/chaser_io

   
Reply all
Reply to author
Forward
0 new messages