All of lore.kernel.org
 help / color / mirror / Atom feed
* device blacklisting and suspend issue
@ 2020-01-15  7:11 Sreenivas.Honnur
  2020-01-15  9:38 ` Sreenivas.Honnur
  0 siblings, 1 reply; 4+ messages in thread
From: Sreenivas.Honnur @ 2020-01-15  7:11 UTC (permalink / raw)
  To: dm-devel


[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]

I have two queries:

  1.  We have an issue with device blacklisting. We add an entry in /etc/multipath.conf" and do "service multipathd reload".
After this to check if device is blacklisted we issue "multipathd show blacklist" command in a loop(with a delay of 1 second).
Sometimes I see that this command takes too much time to come out or sometimes it just hangs. Is this the correct way to check if device is blacklisted? Or is there any other way to do it?


  1.  After suspending (dmsetup suspend wwid) a device,  is there a way to inform multipathd not to make it active if some events happen on this device(like new path added..etc...I see that the table is reloaded and device becomes active)

How to avoid this i.e. the device should be in "suspended" state until I do a "resume" on it, "multipathd" should not enable it until I do "dmsetup resume"







[-- Attachment #1.2: Type: text/html, Size: 6188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 4+ messages in thread

* device blacklisting and suspend issue
  2020-01-15  7:11 device blacklisting and suspend issue Sreenivas.Honnur
@ 2020-01-15  9:38 ` Sreenivas.Honnur
  0 siblings, 0 replies; 4+ messages in thread
From: Sreenivas.Honnur @ 2020-01-15  9:38 UTC (permalink / raw)
  To: dm-devel


[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]

I have two queries:

  1.  We have an issue with device blacklisting. We add an entry in /etc/multipath.conf" and do "service multipathd reload".
After this to check if device is blacklisted we issue "multipathd show blacklist" command in a loop(with a delay of 1 second).
Sometimes I see that this command takes too much time to come out or sometimes it just hangs. Is this the correct way to check if device is blacklisted? Or is there any other way to do it?


  1.  After suspending (dmsetup suspend wwid) a device,  is there a way to inform multipathd not to make it active if some events happen on this device(like new path added..etc...I see that the table is reloaded and device becomes active)

How to avoid this i.e. the device should be in "suspended" state until I do a "resume" on it, "multipathd" should not enable it until I do "dmsetup resume"







[-- Attachment #1.2: Type: text/html, Size: 5439 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 4+ messages in thread

* device blacklisting and suspend issue
@ 2020-01-28 13:22 Sreenivas.Honnur
  0 siblings, 0 replies; 4+ messages in thread
From: Sreenivas.Honnur @ 2020-01-28 13:22 UTC (permalink / raw)
  To: dm-devel

I have below queries, help is appreciated.

1.	We have an issue with device blacklisting. To blacklist a device we add an entry in /etc/multipath.conf" and do "service multipathd reload". After this to check if device is blacklisted we issue "multipathd show blacklist" command in a loop(with a delay of 10 second). Sometimes I see that this command takes too much time to come out or sometimes it just hangs. 
	a. Is this the correct way to check if device is blacklisted? Or is there any other way to do it?
	b. Is "multipathd reload" a async call? Is there a way to know that "multipathd reload" is completed?

2.	After suspending (dmsetup suspend wwid) a device,  is there a way to inform multipathd not to make it active if some events happen on this device(like new path added..etc...I see that the table is reloaded and device becomes active)
How to avoid this i.e. the device should be in "suspended" state until I do a "resume" on it, "multipathd" should not enable it until I do "dmsetup resume"

3.  " blk_cloned_rq_check_limits: over max size limit." Error I have a requirement to change(decrease) the max_sector_kb value of a device, when I do that (using "echo value /sys/block/dm-x/queue/max_sector_kb) I hit above error.
How I can I avoid this error when I change the max_sector_kb value?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* device blacklisting and suspend issue
@ 2020-01-25  7:51 Sreenivas.Honnur
  0 siblings, 0 replies; 4+ messages in thread
From: Sreenivas.Honnur @ 2020-01-25  7:51 UTC (permalink / raw)
  To: dm-devel

I have below queries, help is appreciated.

1.	We have an issue with device blacklisting. To blacklist a device we add an entry in /etc/multipath.conf" and do "service multipathd reload". After this to check if device is blacklisted we issue "multipathd show blacklist" command in a loop(with a delay of 10 second). Sometimes I see that this command takes too much time to come out or sometimes it just hangs. 
	a. Is this the correct way to check if device is blacklisted? Or is there any other way to do it?
	b. Is "multipathd reload" a async call? Is there a way to know that "multipathd reload" is completed?

2.	After suspending (dmsetup suspend wwid) a device,  is there a way to inform multipathd not to make it active if some events happen on this device(like new path added..etc...I see that the table is reloaded and device becomes active)
How to avoid this i.e. the device should be in "suspended" state until I do a "resume" on it, "multipathd" should not enable it until I do "dmsetup resume"

3.  " blk_cloned_rq_check_limits: over max size limit." Error
I have a requirement to change(decrease) the max_sector_kb value of a device, when I do that (using "echo value /sys/block/dm-x/queue/max_sector_kb) I hit above error.
How I can I avoid this error when I change the max_sector_kb value?

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-01-28 13:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-15  7:11 device blacklisting and suspend issue Sreenivas.Honnur
2020-01-15  9:38 ` Sreenivas.Honnur
2020-01-25  7:51 Sreenivas.Honnur
2020-01-28 13:22 Sreenivas.Honnur

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.