-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
px-dev hangs hosts, prevents restarts #45
Comments
The restart block seems to be an issue with the rancher network driver that has been resolved in the internal docker network driver before, I'll move that problem there. |
Update:
|
The BTRFS kernel BUG still happens still happens with |
@svensp this is a kernel bug which was addressed through - https://patchwork.kernel.org/patch/9431679/. To get around this issue you would need to upgrade to kernel v4.10 or higher. |
Setup:
3 Hosts running Portworx.
docker version: 17.03.1-ce, 17.03.2-ce
Portworx Version: portworx/px-dev:1.2.8
Each has 1 Volume at on a volumegroup, which is raid1 on 2 ssd disks
A volume directly on a 3TB HDD was supposed to be added.
Process:
Following https://docs.portworx.com/maintain/scale-up.html:
sudo /opt/pwx/bin/pxctl service maintenance --enter
-- Wait until portworx is back up in maintenance mode --
sudo /opt/pwx/bin/pxctl service drive add /dev/sdc
sudo /opt/pwx/bin/pxctl service maintenance --exit
-- Wait for portworx to return to normal mode --
Portworx stayed in initializing for about 3 minutes, until all 3 Hosts died simultanously with the following log:
Host which was supposed to receive more storage:
Other hosts:
This in itself is already a Problem, but the following error made it even worse:
Docker does not start because Portworx is not available, which starts only after docker is up.
This is a deadlock and I was only able to solve it by removing /var/lib/docker on the hosts
The text was updated successfully, but these errors were encountered: