It seems that in addition to blocking fsck, we should also block swap usage.
The severity of this issue is somewhat limited as the scenario will only happen when
a.) there is a filesystem (or swap) on a disk
b.) there is a (likely stale) entry in /etc/fstab for that disk already
This means that we're kind of limited to either
1. azure instances and resize/redeploy
2. first boot of a an instance snapshootted with stuff in /etc/fstab
3. developer testing (re-partition/setup and rm -Rf /var/lib/cloud && reboot)
It seems that in addition to blocking fsck, we should also block swap usage.
The severity of this issue is somewhat limited as the scenario will only happen when
a.) there is a filesystem (or swap) on a disk
b.) there is a (likely stale) entry in /etc/fstab for that disk already
This means that we're kind of limited to either
1. azure instances and resize/redeploy
2. first boot of a an instance snapshootted with stuff in /etc/fstab
3. developer testing (re-partition/setup and rm -Rf /var/lib/cloud && reboot)