Skip to content
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.

Commit

Permalink
doc: add more troubleshooting guide for machine pool
Browse files Browse the repository at this point in the history
The PR #283 added some
missing code for fixing free space issues. Though in some corner
cases, we would still need to repair the volume manually.

Partly addresses #281
  • Loading branch information
Dongsu Park committed Aug 30, 2018
1 parent 3e32e43 commit ddfcbbb
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions doc/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,18 @@ is the disk image size in bytes:
# btrfs quota disable /var/lib/machines
```

Note that the commands above can fail for some reasons. For example, `umount` can fail because `/var/lib/machines` does not exist. In that case, you might need to create the directory. Or `umount` can fail with `EBUSY`, then you might need to figure out which process blocks umount.

If `/var/lib/machines.raw` does not exist at all, then it means probably that systemd-machined has never initialized the storage pool. So you might need to do the initialization, for example:

```
truncate -s 20G /var/lib/machines.raw
mkfs -t btrfs /var/lib/machines.raw
sudo mount -o loop -t btrfs /var/lib/machines.raw /var/lib/machines
```.
You might also want to set an upper limit for the volume by running `sudo machinectl set-limit 20G`.
## SELinux
To run `kube-spawn`, it is recommended to turn off SELinux enforcing mode:
Expand Down

0 comments on commit ddfcbbb

Please sign in to comment.