search

LINBIT / linstor-client

Python client for LINSTOR
https://docs.linbit.com/docs/linstor-guide/
GNU General Public License v3.0
22 stars 10 forks source link

Consistent on diskless state should be considered as an error #53

Open kvaps opened 3 years ago

kvaps commented 3 years ago

linstor returns no error:

# linstor r l -r one-vm-7674-disk-0
╭────────────────────────────────────────────────────────────────────────────╮
┊ ResourceName       ┊ Node   ┊ Port ┊ Usage  ┊ Conns ┊    State ┊ CreatedOn ┊
╞════════════════════════════════════════════════════════════════════════════╡
┊ one-vm-7674-disk-0 ┊ m11c37 ┊ 7752 ┊ InUse  ┊ Ok    ┊ Diskless ┊           ┊
┊ one-vm-7674-disk-0 ┊ m13c21 ┊ 7752 ┊ Unused ┊ Ok    ┊ UpToDate ┊           ┊
┊ one-vm-7674-disk-0 ┊ m14c24 ┊ 7752 ┊ Unused ┊ Ok    ┊ UpToDate ┊           ┊
╰────────────────────────────────────────────────────────────────────────────╯
# linstor v l -r one-vm-7674-disk-0
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
┊ Node   ┊ Resource           ┊ StoragePool          ┊ VolNr ┊ MinorNr ┊ DeviceName    ┊ Allocated ┊ InUse  ┊    State ┊
╞══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╡
┊ m11c37 ┊ one-vm-7674-disk-0 ┊ DfltDisklessStorPool ┊     0 ┊    1752 ┊ /dev/drbd1752 ┊           ┊ InUse  ┊ Diskless ┊
┊ m13c21 ┊ one-vm-7674-disk-0 ┊ thindata             ┊     0 ┊    1752 ┊ /dev/drbd1752 ┊ 90.02 GiB ┊ Unused ┊ UpToDate ┊
┊ m14c24 ┊ one-vm-7674-disk-0 ┊ thindata             ┊     0 ┊    1752 ┊ /dev/drbd1752 ┊ 90.02 GiB ┊ Unused ┊ UpToDate ┊
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

But actually it is:

root@m11c37:~# drbdadm status one-vm-7674-disk-0
one-vm-7674-disk-0 role:Primary
  disk:Diskless
  m13c21 role:Secondary
    peer-disk:Consistent
  m14c24 role:Secondary
    peer-disk:UpToDate

root@m13c21:~# drbdadm status one-vm-7674-disk-0
one-vm-7674-disk-0 role:Secondary
  disk:UpToDate
  m11c37 role:Primary
    peer-disk:Diskless
  m14c24 role:Secondary
    peer-disk:UpToDate

root@m14c24:~# drbdadm status one-vm-7674-disk-0
one-vm-7674-disk-0 role:Secondary
  disk:UpToDate
  m11c37 role:Primary
    peer-disk:Diskless
  m13c21 role:Secondary
    peer-disk:UpToDate
kvaps commented 3 years ago

resolution:

root@m11c37:~# drbdadm disconnect one-vm-7674-disk-0:m13c21
root@m11c37:~# drbdadm connect one-vm-7674-disk-0:m13c21
root@m11c37:~# drbdadm status one-vm-7674-disk-0
one-vm-7674-disk-0 role:Primary
  disk:Diskless
  m13c21 role:Secondary
    peer-disk:Outdated
  m14c24 role:Secondary
    peer-disk:UpToDate

root@m13c21:~# drbdadm disconnect one-vm-7674-disk-0
root@m13c21:~# drbdadm connect one-vm-7674-disk-0 --discard-my-data 
root@m13c21:~# drbdadm status one-vm-7674-disk-0
one-vm-7674-disk-0 role:Secondary
  disk:Inconsistent
  m11c37 role:Primary
    peer-disk:Diskless
  m14c24 role:Secondary
    replication:SyncTarget peer-disk:UpToDate done:0.48