All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Thimm <Axel.Thimm@ATrpms.net>
To: device-mapper development <dm-devel@redhat.com>
Subject: multipath missed udev-renamed devices
Date: Fri, 22 Jul 2005 02:56:51 +0200	[thread overview]
Message-ID: <20050722005651.GA10987@neu.nirvana> (raw)


[-- 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 --]



                 reply	other threads:[~2005-07-22  0:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050722005651.GA10987@neu.nirvana \
    --to=axel.thimm@atrpms.net \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.