Mailing List Archive

LINSTOR: read-only DRBD volume after node restart
Hello all,

I set up storage for Kubernetes using this article:
https://vitobotta.com/2019/08/07/linstor-storage-with-kubernetes

Everything works fine unless first reboot of the cluster node. After
system restart I am not able to mount any existing DRBD device in RW mode.

root@worker1:~# mount /dev/drbd1003 /mnt
mount: /mnt: WARNING: device write-protected, mounted read-only.

I think this happens due to some synchronization issues between cluster
node. Have noticed that linstor volume list shows different number of
allocated bytes on different node members:

LINSTOR ==> v l
???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
? Node    ? Resource                                 ? StoragePool  ?
VolNr ? MinorNr ? DeviceName    ? Allocated ? InUse  ?    State ?
???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
? worker1 ? pvc-74415818-e108-43a1-8d16-047416ca3755 ? linstor-pool
?     0 ?    1003 ? /dev/drbd1003 ?  4.75 GiB ? Unused ? UpToDate ?
? worker2 ? pvc-74415818-e108-43a1-8d16-047416ca3755 ? linstor-pool
?     0 ?    1003 ? /dev/drbd1003 ?  4.80 GiB ? Unused ? UpToDate ?
? worker3 ? pvc-74415818-e108-43a1-8d16-047416ca3755 ? linstor-pool
?     0 ?    1003 ? /dev/drbd1003 ?  4.53 GiB ? Unused ? UpToDate ?
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

At the moment the only working solution to fix the problem I have
invented is to create new resource and copy data from read-only mount to
the new one.

How to fix it properly?

Thanks,

Vadim


_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user
LINSTOR: read-only DRBD volume after node restart [ In reply to ]
Hello all,

I set up storage for Kubernetes using this article:
https://vitobotta.com/2019/08/07/linstor-storage-with-kubernetes

Everything works fine unless first reboot of the cluster node. After
system restart I am not able to mount any existing DRBD device in RW mode.

root@worker1:~# mount /dev/drbd1003 /mnt
mount: /mnt: WARNING: device write-protected, mounted read-only.

I think this happens due to some synchronization issues between cluster
node. Have noticed that linstor volume list shows different number of
allocated bytes on different node members:

LINSTOR ==> v l
???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
? Node    ? Resource                                 ? StoragePool  ?
VolNr ? MinorNr ? DeviceName    ? Allocated ? InUse  ?    State ?
???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
? worker1 ? pvc-74415818-e108-43a1-8d16-047416ca3755 ? linstor-pool
?     0 ?    1003 ? /dev/drbd1003 ?  4.75 GiB ? Unused ? UpToDate ?
? worker2 ? pvc-74415818-e108-43a1-8d16-047416ca3755 ? linstor-pool
?     0 ?    1003 ? /dev/drbd1003 ?  4.80 GiB ? Unused ? UpToDate ?
? worker3 ? pvc-74415818-e108-43a1-8d16-047416ca3755 ? linstor-pool
?     0 ?    1003 ? /dev/drbd1003 ?  4.53 GiB ? Unused ? UpToDate ?
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

At the moment the only working solution to fix the problem I have
invented is to create new resource and copy data from read-only mount to
the new one.

How to fix it properly?

Thanks,

Vadim


_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user