StorageException: Failed to mkfs /dev/drbd1002 #641
Comments
|
Please try to update to the latest version. It also looks like this was not a fresh install? Otherwise, why would there be any resources? This Looks like the resource (which already existed) is still in use somewhere. So someone has the still mounted or similar. Clean that up first (check the resource state |
|
I will try to upgrade to the latest version, but this is a fresh install. We plan to use Linstor in production, but before that we are doing automated testing by installing fresh Kubernetes on three VMs and then via Flux CD piraeus operator. This installation was started on Friday evening and this morning I saw the installation status and found the errors I describe in this issue. The output of the The PVC pvc-80745669-9bf4-4776-9865-f6f419c57863 is used by the monitoring, which cannot start: |
|
So it looks like Could you please try to run: It looks like the CSI driver later tried to create the volume again and somehow determined that the volume already exists, which lead to it being bound. I would recommend deleting the PVC and PV and letting it be recreated. |
|
Here is output of the commands |
|
Ok, this looks like a bug in LINSTOR that does not properly restore the resource to secondary after the mkfs call fails. Still leaves the issue how it can be that /dev/drbd1002 does not exist at this point. I have no idea how that can happen. To fully clean up the volume: Then, run |
|
Your last suggestion worked, I was able to reinstall the monitoring. What would you recommend now? |
|
Yes, please upgrade and see if it happens again. In case you encounter an issue, run Then copy the created file from the pod to your host and attach it to the issue |
|
@WanzenBug , I am currently testing the latest version of Piraeus Operator v2.5.0 and so far the problem described in this issue has not reoccurred. However, I have just reproduced again a problem that I described in another issue: LINBIT/linstor-server#396 . Since I never got a response in the linstor-server project, should I recreate the issue in this (piraeus-operator) project? |
|
Yes, this is an issue more appropriate for the piraeus project. |
After installing piraeus-operator I get the error message
StorageException: Failed to mkfs /dev/drbd1002.Kubernetes version: v1.28.8
Priaeus operator: v2.3.0
Piraeus server: v1.25.1
Linstor is installed with the following satellite configuration
After installation I get a number of errors:
Here are the error reports:
StorageException: Failed to mkfs /dev/drbd1002Resource 'pvc-80745669-9bf4-4776-9865-f6f419c57863' on node 'k8s-m2' is still in use.Generated resource file for resource 'pvc-80745669-9bf4-4776-9865-f6f419c57863' is invalid.(Node: 'k8s-m2') Generated resource file for resource 'pvc-80745669-9bf4-4776-9865-f6f419c57863' is invalid.Generated resource file for resource 'pvc-80745669-9bf4-4776-9865-f6f419c57863' is invalid.Output of LVM's
pvs; vgs; lvs;on cluster nodes:The text was updated successfully, but these errors were encountered: