* multipath missed udev-renamed devices
@ 2005-07-22 0:56 Axel Thimm
0 siblings, 0 replies; only message in thread
From: Axel Thimm @ 2005-07-22 0:56 UTC (permalink / raw)
To: device-mapper development
[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]
In order to be able to handle multipath devices better (avoid anything
else, but multipath to access the single paths) I moved the paths from
the devices to different names:
# ls /dev/*sd*
/dev/hsv100-sdb /dev/hsv100-sdd /dev/hsv100-sde /dev/sda /dev/sda2
/dev/hsv100-sdc /dev/hsv100-sdd1 /dev/hsv100-sde1 /dev/sda1
The /dev/sda is the system disk, while the 4 /dev/hsv100-sd* devices
are the 4 paths to an EVA 3000.
Unfortuantely multipath does not see the /dev/hsv100-sd* devices. This
is because after querying sysfs devinfo in libmultipath/discovery.c
also wants to get a file descriptor on the device.
But it is using the kernel's device name, not the one from udev, the
access fails, and the path gets dropped.
What can be done to fix this? multipath needs the fd on the device for
further queries (serial and state). Should multipath call udev to get
the device's name?
Is there a workaround I can use now to get multipath on my
/dev/hsv100-sd* devices running?
Thanks!
--
Axel.Thimm at ATrpms.net
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-07-22 0:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-22 0:56 multipath missed udev-renamed devices Axel Thimm
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.