Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-7510

fstab entries can be written in bad order

    Details

    • Template:
    • Team:
      Platform OS
    • Story Points:
      2
    • Sprint:
      Client 2015-07-22, Client 2015-12-02
    • UX Priority:
      Normal

      Description

      Given the following fstab content in /tmp/fstab

      /dev/sda1       /       ext4         defaults,relatime,errors=remount-ro           0    1       
      /dev/sda2       /usr/share      ext4    defaults,noatime,errors=remount-ro      0       2
      

      the following manifest

      bundle exec puppet apply -e 'mount { "/usr": ensure => "present", device => "/dev/sda3", target => "/tmp/fstab" }'
      

      leads to the following fstab.

      # HEADER: This file was autogenerated at 2015-05-17 22:09:35 +0200
      # HEADER: by puppet.  While it can still be managed manually, it
      # HEADER: is definitely not recommended.
      /dev/sda1	/	ext4	defaults,relatime,errors=remount-ro	0	1
      /dev/sda2	/usr/share	ext4	defaults,noatime,errors=remount-ro	0	2
      /dev/sda3	/usr			0	0
      

      Assuming that all contents of /usr, including the share/ mount point are moved to the new device, the older filesystem /usr/share will not be mounted on system startup anymore. Older systems can even become unbootable.

      It would be preferable for Puppet to bring the filesystems into an order that ensures that they are processed properly at boot.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                branan Branan Riley
                Reporter:
                ffrank Felix Frank
                QA Contact:
                Eric Thompson
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support