Hi, On Tuesday, 14. December 2004 21:01, christophe varoqui wrote: [...] > > Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:144 > > ...................... (more the the rest of the Luns) > > Mostly good, but the multipath tool didn't configured any multipath > map ... we'll need to track that. I got the same, needed to create the maps "manually" by dmsetup to get any further. > > > Followed by the following after a little while: > > The little while is the time for the fd leak to fill the entire fd > space ... upgrade to 0.4.0 Is this fd leak related to the specific hardware? > > > Dec 13 21:12:40 netsrv83 multipathd: 67:64 : readsector0 checker reports > > path is down > > Dec 13 21:12:40 netsrv83 multipathd: 67:80 : readsector0 checker reports > > path is down > > Dec 13 21:12:40 netsrv83 multipathd: 67:96 : readsector0 checker reports > > path is down > > ... > > > Running the command multipath -v 2 doesn't yield any output and /dev had > > no dm device created. > > That the heart of the problem. you might get dm-devices after manual creation of device maps and /etc/udev/udev.rules: KERNEL="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", \ NAME="%k", SYMLINK="%c" Regards, Andreas Huck