From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: RE: not dynamically creating disk device nodes
Date: Thu, 12 Apr 2007 22:15:11 +0000 [thread overview]
Message-ID: <1176416111.17474.6.camel@lov.localdomain> (raw)
In-Reply-To: <3ae72650704110217k73ebec17wf92af95654d197fc@mail.gmail.com>
On Thu, 2007-04-12 at 18:02 -0400, Leisner, Martin wrote:
> That's what's happening. When I crate the block device, there's no
> MAJOR/MINOR.
>
> It seems to be making character devices fine (I modified some of the
> LDD3 examples to create a class,
> and it works fine).
>
> For character devices, udev is opening the /class/<name>/dev file.
> For block devices, its NOT opening the /block/<partition name>/dev
> file.
We added stuff to the kernel, to make udev more reliable, and this
version of udev depends on a newer kernel. I suggest running an older
udev or a newer kernel.
> What's a good way to debug udevd? Is there a way to run it without
> forks?
It will always fork, the daemon just handles the event queue.
> Or is there magic to debug a forking process (catch/follow-fork seems
> crude and only works
> once).
You can set the log level in /etc/udev/udev.conf or dynamically with
udevcontrol. And strace -f should work too, if the log does not provide
the needed information.
Kay
> > -----Original Message-----
> > From: linux-hotplug-devel-bounces@lists.sourceforge.net
> > [mailto:linux-hotplug-devel-bounces@lists.sourceforge.net] On
> > Behalf Of Kay Sievers
> > Sent: Wednesday, April 11, 2007 5:18 AM
> > To: Leisner, Martin
> > Cc: linux-hotplug-devel@lists.sourceforge.net
> > Subject: Re: not dynamically creating disk device nodes
> >
> > On 4/9/07, Leisner, Martin <Martin.Leisner@xerox.com> wrote:
> > > I'm trying to use udev-092 on linux-2.6.10.
> > >
> > > Most things work.
> > >
> > > udevstart works fine.
> > >
> > > But when I start playing around with fdisk, the device nodes aren't
> > > getting erased/created
> > > for the hard drive (udevstart had no problem figuring this out)..
> > >
> > > udevd says:
> > >
> > > udevd[1163]: udev_event_run: seq 707 forked, pid [1168],
> > 'add' 'block',
> > > 0 seconds old
> > > udevd-event[1168]: udev_db_get_device: no db file to read
> > > /dev/.udev/db/block@sda: No such file or directory
> > > udevd-event[1168]: udev_db_get_device: no db file to read
> > > /dev/.udev/db/block@sda: No such file or directory
> > > udevd-event[1168]: run_program: '/lib/udev/vol_id --export
> > > /dev/.tmp-0-0'
> >
> > Udev does not seem to get the correct major/minor number for the
> > device, "0-0" looks wrong.
> >
> > It is likely, that the udev daemon (10 months old) expects
> > MAJOR/MINOR-values in the event environment, but that kernel (2.5
> > years old) doesn't export it.
> >
> > Udevstart reads that information from the "dev" file in sysfs, that's
> > why it may work just fine.
> >
> > Kay
> >
> > --------------------------------------------------------------
> > -----------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the
> > chance to share your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge
> > &CIDÞVDEV
> > _______________________________________________
> > 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
> >
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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
next prev parent reply other threads:[~2007-04-12 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 9:17 not dynamically creating disk device nodes Kay Sievers
2007-04-12 21:57 ` Leisner, Martin
2007-04-12 22:15 ` Kay Sievers [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-09 21:54 Leisner, Martin
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=1176416111.17474.6.camel@lov.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