Guido Guenther wrote: > Hi Hannes, > On Fri, Jul 20, 2007 at 09:24:15AM +0200, Hannes Reinecke wrote: >> Hmm. multipathd really should react to the 'remove' events for sdX. >> Checking ... >> >> Looks as if it does. And it even is supposed to stop the path checker. >> >> Care to run multipathd with full debugging (ie -v 4) and post the output? >> My guess is that somehow the path checker is not stopped and the fd is kept >> open, so that the device is not released properly. > This even happens with no multipathd running on a Clariion with qla2xx. > So multipathd can't be at fault here, can it? Also with multipathd > running the device nodes in /dev/ and the sysfs nodes in /sys/block get > removed properly (at least it looks like to me). Any hints where else to > start digging? Removing from /dev and /sys in not sufficient, sadly. The memory is only released after the last reference has gone. So all fd's have to be closed (ie multipathd and the path checkers have to have this path disabled) and no device-mapper table must reference it. So easiest way is infact to have multipathd run with -v 4, as this will tell you exactly if multipathd has stopped the path checker. The device-mapper tables can be checked manually with dmsetup. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage hare@xxxxxxx +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
