Investigate whether we need fsck in CentOS Automotive images

[ericcurtin]

On fast hardware we spend 30ms each fscking /boot and /root ext4 partitions. On common Automotive hardware, this probably translates to around ~100ms.

systemd-analyze plot | grep -i fsck
  <text class="left" x="228.567" y="1474.000">system-systemd\x2dfsck.slice</text>
  <text class="left" x="232.540" y="1934.000">systemd-fsck-root.service (33ms)</text>
  <text class="left" x="253.543" y="2314.000">systemd-fsck@dev-disk-by\x2duuid-156f0420\x2d627b\x2d4151\x2dae6f\x2dfda298097515.service (29ms)</text>

note we plan on using composefs also, which can detect some bad data.

We should see what fsck is doing exactly during boot time here on ext4 partitions and see if it's worth the extra milliseconds it adds to boot.

[ericcurtin]

It's less beneficial, but we could do fsck on shutdown potentially after we have unmounted.