From: "C. Linus Hicks" <lhicks@nc.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Assumptions in start_udev regarding the loop device
Date: Fri, 11 Feb 2005 16:46:21 +0000 [thread overview]
Message-ID: <1108140382.5891.22.camel@lh4.linush.net> (raw)
In-Reply-To: <1108016718.4753.86.camel@lh4.linush.net>
On Thu, 2005-02-10 at 16:40 +0100, Harald Hoyer wrote:
> Marco d'Itri wrote:
> > On Feb 10, Kay Sievers <kay.sievers@vrfy.org> wrote:
> >
> >
> >>Why do we need to create these nodes with a script? Loop-devices are
> >
> > Because nothing loads the module.
>
> correct... chicken and egg... no module autoloading without a device node to
> trigger it, and no device node created by udev without the loaded module.
The following in from an interaction on the nahant-beta-list:
> On Thu, 2005-02-10 at 15:31 -0500, Jeremy Katz wrote:
> > So, the reasoning for this is that loop devices are something of a
> > chicken and egg problem. You normally get the loop module loaded by
> > opening /dev/loop0 and getting a kmod call. But, with udev, the device
> > node doesn't get created until the module is loaded. So, we go ahead
> > and create the first n loop devs now and so after you mount your first
> > one, the loop module will get loaded (with your option
> > from /etc/modprobe.conf) and then the rest of the devices will get
> > created.
However, this is not what happens on my system, using the kernel from
the RHEL4 beta-2 CD.
[root@lh4 dev]# uname -a
Linux lh4.linush.net 2.6.9-1.648_EL #1 Tue Oct 26 12:15:22 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux
With the above kernel, if I use a value greater than 224 for the
max_loop option in modprobe.conf, I get an out of memory error, but
that's not a hotplug issue. When the module is successfully loaded, I
get this:
Feb 10 18:34:15 lh4 kernel: loop: loaded (max 224 devices)
Feb 10 18:35:06 lh4 hald[2710]: Timed out waiting for hotplug event 327. Rebasing to 329
Feb 10 18:35:10 lh4 hald[2710]: Timed out waiting for hotplug event 336. Rebasing to 339
Feb 10 18:35:18 lh4 udev[4842]: creating device node '/dev/loop0'
Feb 10 18:35:20 lh4 hald[2710]: Timed out waiting for hotplug event 346. Rebasing to 349
Feb 10 18:35:23 lh4 udev[4848]: creating device node '/dev/loop1'
Feb 10 18:35:23 lh4 udev[4842]: error: timeout reached, event probably not handled correctly
Feb 10 18:35:25 lh4 05-pam_console.dev[4949]: Restoring console permissions for /dev/loop0
Feb 10 18:35:35 lh4 hald[2710]: Timed out waiting for hotplug event 356. Rebasing to 359
Feb 10 18:36:02 lh4 hald[2710]: Timed out waiting for hotplug event 366. Rebasing to 369
Feb 10 18:36:18 lh4 hald[2710]: Timed out waiting for hotplug event 376. Rebasing to 379
Feb 10 18:36:33 lh4 hald[2710]: Timed out waiting for hotplug event 386. Rebasing to 389
Feb 10 18:37:00 lh4 hald[2710]: Timed out waiting for hotplug event 396. Rebasing to 399
Feb 10 18:37:15 lh4 hald[2710]: Timed out waiting for hotplug event 406. Rebasing to 409
Feb 10 18:37:42 lh4 hald[2710]: Timed out waiting for hotplug event 416. Rebasing to 419
Feb 10 18:38:00 lh4 hald[2710]: Timed out waiting for hotplug event 426. Rebasing to 429
Feb 10 18:38:24 lh4 hald[2710]: Timed out waiting for hotplug event 436. Rebasing to 439
Feb 10 18:38:40 lh4 hald[2710]: Timed out waiting for hotplug event 446. Rebasing to 449
Feb 10 18:39:01 lh4 hald[2710]: Timed out waiting for hotplug event 456. Rebasing to 459
Feb 10 18:39:20 lh4 hald[2710]: Timed out waiting for hotplug event 466. Rebasing to 469
Feb 10 18:39:36 lh4 hald[2710]: Timed out waiting for hotplug event 476. Rebasing to 479
Feb 10 18:40:01 lh4 hald[2710]: Timed out waiting for hotplug event 486. Rebasing to 489
Feb 10 18:40:17 lh4 hald[2710]: Timed out waiting for hotplug event 496. Rebasing to 499
Feb 10 18:40:38 lh4 hald[2710]: Timed out waiting for hotplug event 506. Rebasing to 509
Feb 10 18:40:58 lh4 hald[2710]: Timed out waiting for hotplug event 516. Rebasing to 519
Feb 10 18:41:16 lh4 hald[2710]: Timed out waiting for hotplug event 526. Rebasing to 529
Feb 10 18:41:39 lh4 hald[2710]: Timed out waiting for hotplug event 536. Rebasing to 539
Feb 10 18:46:24 lh4 udev[6272]: creating device node '/dev/loop196'
Feb 10 18:46:26 lh4 udev[6272]: error: timeout reached, event probably not handled correctly
Feb 10 18:46:27 lh4 udev[6274]: creating device node '/dev/loop206'
Feb 10 18:46:27 lh4 05-pam_console.dev[6284]: Restoring console permissions for /dev/loop196
Feb 10 18:46:28 lh4 udev[6276]: creating device node '/dev/loop216'
Feb 10 18:46:28 lh4 udev[6277]: creating device node '/dev/loop217'
Feb 10 18:46:29 lh4 05-pam_console.dev[6290]: Restoring console permissions for /dev/loop206
Feb 10 18:46:29 lh4 udev[6278]: creating device node '/dev/loop218'
Feb 10 18:46:30 lh4 05-pam_console.dev[6296]: Restoring console permissions for /dev/loop216
Feb 10 18:46:30 lh4 05-pam_console.dev[6298]: Restoring console permissions for /dev/loop217
Feb 10 18:46:30 lh4 05-pam_console.dev[6300]: Restoring console permissions for /dev/loop218
And I end up with this in /dev:
[root@lh4 dev]# ls -l loop*
brw-rw---- 1 root disk 7, 0 Feb 10 18:30 loop0
brw-rw---- 1 root disk 7, 1 Feb 10 18:30 loop1
brw-rw---- 1 root disk 7, 196 Feb 10 18:46 loop196
brw-r----- 1 root disk 7, 2 Feb 10 18:30 loop2
brw-rw---- 1 root disk 7, 206 Feb 10 18:46 loop206
brw-rw---- 1 root disk 7, 216 Feb 10 18:46 loop216
brw-rw---- 1 root disk 7, 217 Feb 10 18:46 loop217
brw-rw---- 1 root disk 7, 218 Feb 10 18:46 loop218
brw-r----- 1 root disk 7, 3 Feb 10 18:30 loop3
brw-r----- 1 root disk 7, 4 Feb 10 18:30 loop4
brw-r----- 1 root disk 7, 5 Feb 10 18:30 loop5
brw-r----- 1 root disk 7, 6 Feb 10 18:30 loop6
brw-r----- 1 root disk 7, 7 Feb 10 18:30 loop7
Is this a hotplug issue? Is it Red Hat induced? Could it be an issue
specific to the architecture?
--
C. Linus Hicks <lhicks at nc dot rr dot com>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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-02-11 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 6:25 Assumptions in start_udev regarding the loop device C. Linus Hicks
2005-02-10 8:03 ` Kay Sievers
2005-02-10 9:09 ` Marco d'Itri
2005-02-10 15:40 ` Harald Hoyer
2005-02-11 16:46 ` C. Linus Hicks [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=1108140382.5891.22.camel@lh4.linush.net \
--to=lhicks@nc.rr.com \
--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).