Closed maikotz closed 7 years ago
Just a quick feedback on this one.
Inspecting the pwx container didn't really help, I could not find out where the .lock files where located to manually delete them and try to initialise the node manually. Even deleting the BTRFS subvolume didn't help, so I looked into just recovering the data from the test containers.
This was surprisingly easy, as everything is just based on BTRFS, so I mounted my device (/dev/loop here) and found all created volumes there which I could manually ext4 mount and save the data. It didn't really matter to me, but might be helpful for someone else if in need.
sudo mount /data/storage.bin /mnt
mkdir /tmp/mnts/; for i in [0-9]*; do mkdir /tmp/mnts/${i}; sudo mount ${i}/pxdev /tmp/mnts/${i}; done
@maikotz sorry for the delay in getting to this. Do you have still have the logs for the px container in this case?
Hi there,
after rebooting my px-dev host can't start the storage and is stuck in "initializing". Is there any way to force quorum and enable / start this host?
I'm running px version: pxctl version 1.1.6-cb1bbeb
In the px-dev container I get some warning about locks and after w while the container restarts
time="2017-04-26T20:46:11Z" level=warning msg="Lock pwx/5ac2ed6f-7e4e-4e1d-8e8c-3a6df1fb61a7/storage/locks/1056637145994285341.lock locked for 285 seconds, tag: {NodeID:94e7b4e6-6bf8-41a5-bfa0-45bfe6afdd22,FuncID:postVolumeUsage}"
pwxctl status says:
cluster list:
Is this because it is not a 3 node cluster and therefore no quorum can be reached or is this just a side effect since pwx can not initialize the storage because of the .lock files?