Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Crash on one LUN while creating new LUNs

Pages: 1 2

did this happen after you upgraded to 2.5.3 ?

was this server an iSCSI service before ?

on the server, does /opt/petasan/config/node_info.json : does it show the is_iscsi flag as true ?

The flag is true. I was not aware that this server had this flag until now so I recognized it after upgrade (it has never shown up in the gui). Nevertheless how to bring it back into the gui or howto move paths the correct server and set flag to false?

turn fencing off

set the flag to false manually ( can be done in 2.6 from ui )

do a restart of iscsi service

systemctl restart petasan-iscsi

wait for paths to move to other servers

systemctl stop petasan-iscsi

turn fencing on

Restarting does not move the paths, shall I stop it?

In an old email some years ago there was mentioned to do a

consul kv put PetaSAN/Nodes/NODE_NAME @/opt/petasan/config/node_info.json

after changing the flag. Should I?

 

Also using /opt/petasan/scripts/util/move_path.py leads to the ip beeing removed shortly but reassign after. The ip comes back to the server. Tried it 3 times, maybe it is because the other server have more ips to serve.

if you change the flag in consul as you showed, you should be able to use the move path in the ui to move paths away, the iscsi service should be running.

another option is to have the set to false both locally and in consul then reboot the node if this is possible.

I think I got it:

  • I turned fencing off
  • changed node_info.json
  • systemctl stop petasan-iscsi
  • uploaded config to consul
  • used move_path.py to move the paths (needs petasan-iscsi to be stopped otherwise ips come back to the same server)
  • rebooted the host (maybe not needed)
  • created a new disk just to make sure it does not has paths from this host
  • turned fencing on

 

Great 🙂

 

Pages: 1 2