Previously when the block device was resized the partition table was also
resized but the filesystem was not. For an increase from 64GiB to 128GiB
the console showed:
* Configuring host block device .../dev/vda1: clean, 62/4194304 files, 604445/16776960 blocks
Resizing disk partition: Unpartitioned space /dev/vda: 64 GiB, 68719476736 bytes, 134217728 sectors
resize2fs 1.43.3 (04-Sep-2016)
Please run 'e2fsck -f /dev/vda1' first.
/dev/vda1: clean, 62/4194304 files, 604445/16776960 blocks
This patch makes `resize2fs` happy by running `e2fsck -f` beforehand as
requested.
Signed-off-by: David Scott <dave.scott@docker.com>
- use our own code rather than Alpine setup-disk
- remove alpine setup code as not needed
- do not create swap partitions
- create swap file on desktop editions for now (may remove)
Fix#619
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
- run bootmisc before sysklogd so symlinks from /var/run to
/run are created
- recreate symlinks that bootmisc created when we remount /var
until this gets moved earlier
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
This reverts commit 4dd5dca106.
Fix#710 where system hangs after klogd startup on AWS. Possibly
also affects Windows too. Still unclear why but lets revert and
continue investif=gating.
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
So that we can write to /var early, move filesystem formatting as early as possible.
Adds a dummy fsck service, as we already do fsck in format script.
Replaces #535
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
Use fsck -p to fix errors that are fixable.
Note this will recreate the filesystem on fatal errors.
Fix#665
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
