Skip to content
Permalink
Browse files

New GCE images are getting barrier=1 set in fstab on XFS

XFS doesn't support barrier=1 - specifically remove it until we
understand why it is happening.
  • Loading branch information...
smarterclayton committed Aug 4, 2017
1 parent 4665f19 commit 4bf7cf17d4bf576e7e543c39bfdfa797edaf72ca
Showing with 9 additions and 1 deletion.
  1. +9 −1 playbooks/image.yaml
@@ -65,14 +65,22 @@
post_tasks:
- name: Add the Google Cloud repo
yum_repository:
name: google-cloud-compute
name: google-cloud
description: Google Cloud Compute
baseurl: https://packages.cloud.google.com/yum/repos/google-cloud-compute-el7-x86_64
gpgkey: https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
gpgcheck: yes
repo_gpgcheck: yes
state: present
when: ansible_os_family == "RedHat"

# GCE instances are starting with xfs AND barrier=1, which is only for extfs.
- name: Verify fstab entries are correct for XFS volumes
hosts: build_instance_ips
tasks:
- name: Remove barrier=1 from XFS fstab entries
command: sed -i -e 's/xfs\(.*\)barrier=1/xfs\1/g; s/, / /g' /etc/fstab

- name: Build image
hosts: build_instance_ips
roles:

0 comments on commit 4bf7cf1

Please sign in to comment.
You can’t perform that action at this time.