ForumGeneral DiscussionPassed queue_depth: 512 exceeds T …

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

Passed queue_depth: 512 exceeds TCM/SE_Device MAX TCQ: 256

wailer
75 Posts

February 27, 2019, 1:03 pm

Quote from wailer on February 27, 2019, 1:03 pm

I am seeing this message in all nodes of my cluster , only one time as of now.

I have been reading it might be caused by the queue length from controller or disk , but quite lost on this.

Is it something I should worry about ? Any idea how to solve it?

I am seeing this message in all nodes of my cluster , only one time as of now.

I have been reading it might be caused by the queue length from controller or disk , but quite lost on this.

Is it something I should worry about ? Any idea how to solve it?

#1

admin
2,930 Posts

February 27, 2019, 1:44 pm

Quote from admin on February 27, 2019, 1:44 pm

look in the config file:
/opt/petasan/config/tuning/current/lio_tunings
if under "storage_objects": it shows
"queue_depth": 512
change it to
"queue_depth": 256

you should move the paths to other nodes then back, this will create a new connection with updated queue depth

look in the config file:
/opt/petasan/config/tuning/current/lio_tunings
if under "storage_objects": it shows
"queue_depth": 512
change it to
"queue_depth": 256

you should move the paths to other nodes then back, this will create a new connection with updated queue depth

#2

wailer
75 Posts

February 27, 2019, 5:21 pm

Quote from wailer on February 27, 2019, 5:21 pm

Hi , I tried this , but path reassignment is always failing.

27/02/2019 18:17:41 INFO Path 00002/1 acquired successfully
27/02/2019 18:17:41 INFO LIO add_target() disk wwn is 00002
27/02/2019 18:17:38 INFO Image image-00002 mapped successfully.
27/02/2019 18:17:37 INFO Found pool:pool1 for disk:00002 via consul
27/02/2019 18:17:37 INFO PetaSAN cleaned iqns.
27/02/2019 18:17:37 INFO Image image-00002 unmapped successfully.
27/02/2019 18:17:37 INFO LIO deleted Target iqn.2016-05.com.petasan:00002
27/02/2019 18:17:37 INFO LIO deleted backstore image image-00002
27/02/2019 18:17:36 INFO PetaSAN unlocked any consul locks not configured in this node.
27/02/2019 18:17:36 INFO Unlock path 00002/1
27/02/2019 18:17:34 INFO Path 192.168.74.200 status updated to 3
27/02/2019 18:17:34 INFO Updating path 192.168.74.200 status to 3
27/02/2019 18:17:34 ERROR Move action,cannot clean newtwork config for disk 00002 path 0.
27/02/2019 18:17:34 INFO Move action,cleaned disk 00002 path 0.
27/02/2019 18:17:34 INFO Found pool:pool1 for disk:00002 via consul
27/02/2019 18:17:34 INFO Path 192.168.74.200 status updated to 0
27/02/2019 18:17:34 INFO Updating path 192.168.74.200 status to 0
27/02/2019 18:17:34 INFO Reassignment paths script invoked to run clean action.

 

Thanks,

Hi , I tried this , but path reassignment is always failing.

27/02/2019 18:17:41 INFO Path 00002/1 acquired successfully
27/02/2019 18:17:41 INFO LIO add_target() disk wwn is 00002
27/02/2019 18:17:38 INFO Image image-00002 mapped successfully.
27/02/2019 18:17:37 INFO Found pool:pool1 for disk:00002 via consul
27/02/2019 18:17:37 INFO PetaSAN cleaned iqns.
27/02/2019 18:17:37 INFO Image image-00002 unmapped successfully.
27/02/2019 18:17:37 INFO LIO deleted Target iqn.2016-05.com.petasan:00002
27/02/2019 18:17:37 INFO LIO deleted backstore image image-00002
27/02/2019 18:17:36 INFO PetaSAN unlocked any consul locks not configured in this node.
27/02/2019 18:17:36 INFO Unlock path 00002/1
27/02/2019 18:17:34 INFO Path 192.168.74.200 status updated to 3
27/02/2019 18:17:34 INFO Updating path 192.168.74.200 status to 3
27/02/2019 18:17:34 ERROR Move action,cannot clean newtwork config for disk 00002 path 0.
27/02/2019 18:17:34 INFO Move action,cleaned disk 00002 path 0.
27/02/2019 18:17:34 INFO Found pool:pool1 for disk:00002 via consul
27/02/2019 18:17:34 INFO Path 192.168.74.200 status updated to 0
27/02/2019 18:17:34 INFO Updating path 192.168.74.200 status to 0
27/02/2019 18:17:34 INFO Reassignment paths script invoked to run clean action.

 

Thanks,

#3

admin
2,930 Posts

February 27, 2019, 6:42 pm

Quote from admin on February 27, 2019, 6:42 pm

After changing the lio tunings, can you reboot

After changing the lio tunings, can you reboot

#4

wailer
75 Posts

February 27, 2019, 10:45 pm

Quote from wailer on February 27, 2019, 10:45 pm

Sure,  then I should restart all nodes one by one to apply this settings.

About the path re-assignment, any idea why is not working ?

Sure,  then I should restart all nodes one by one to apply this settings.

About the path re-assignment, any idea why is not working ?

#5

admin
2,930 Posts

February 28, 2019, 6:39 am

Quote from admin on February 28, 2019, 6:39 am

i suspect it is related to the same thing, let me know if the issue persists.

i suspect it is related to the same thing, let me know if the issue persists.

#6

wailer
75 Posts

February 28, 2019, 10:06 am

Quote from wailer on February 28, 2019, 10:06 am

Just applied all tuning settings to all nodes, the error message about queue_depth disappeared. I am opening a new post about path the reassignment issue as this one got solved.

Thx!

Just applied all tuning settings to all nodes, the error message about queue_depth disappeared. I am opening a new post about path the reassignment issue as this one got solved.

Thx!

#7

Post Reply: Passed queue_depth: 512 exceeds TCM/SE_Device MAX TCQ: 256

Cancel