From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem with udev (and/or hotplug)
Date: Thu, 27 Jan 2005 10:00:32 +0000 [thread overview]
Message-ID: <1106820033.7024.33.camel@localhost.localdomain> (raw)
In-Reply-To: <D18A13F01D850B409793C6C3FA5E0389012EEE57@SRVRE02.rdm.cz>
On Thu, 2005-01-27 at 10:06 +0100, Marek.Uher@t-mobile.cz wrote:
> Hello all,
>
> I migrated my server from DevFS to udev. The reason for this migration was plan
> to connect this server to IBM ESS 2105 Shark SAN storage over multipath tools
> from Christophe Varoqui. Everything was OK up to upgrade to udev 0.5.20.
There was never such a version number for udev. What does:
udevinfo -V
print?
> I was
> in trouble to bring up my server after upgrading to this version. I randomly
> miss symbolic links for my local SCSI disk in /dev after reboot. Normally I have
> these symbolic links in /dev:
>
> sda -> scsi/host0/bus0/target0/lun0/disc
> sda1 -> scsi/host0/bus0/target0/lun0/part1
> sda2 -> scsi/host0/bus0/target0/lun0/part2
> sda3 -> scsi/host0/bus0/target0/lun0/part3
> sda4 -> scsi/host0/bus0/target0/lun0/part4
> sda5 -> scsi/host0/bus0/target0/lun0/part5
> sda6 -> scsi/host0/bus0/target0/lun0/part6
> sda7 -> scsi/host0/bus0/target0/lun0/part7
> sda8 -> scsi/host0/bus0/target0/lun0/part8
> sda9 -> scsi/host0/bus0/target0/lun0/part9
>
>
> But sometimes (after reboot) I miss some of these links. For example: sda2,
> sda6, and etc (periodically only one symbolic link is missing). Sometime I
> found all symbolic links.
What does:
udevinfo -q all -p /block/sda2
print - "sda2" replaced whith the device name you miss the symlink for?
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-01-27 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 9:06 Problem with udev (and/or hotplug) Marek.Uher
2005-01-27 10:00 ` Kay Sievers [this message]
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=1106820033.7024.33.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).