public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Joe <joecool1029@gmail.com>, linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
Date: Mon, 2 May 2005 20:14:21 -0700	[thread overview]
Message-ID: <20050503031421.GA528@kroah.com> (raw)
In-Reply-To: <d4757e6005050219514ece0c0a@mail.gmail.com>

On Mon, May 02, 2005 at 10:51:24PM -0400, Joe wrote:
> Ok, first off I'd like to say, I am on 2.6.12-rc3-mm2, and this issue
> is not fixed at all.  Secondly, I'd like to say that I've pinpointed
> it a bit more.  It appears only Empty partitions (type 0 in fdisk) do
> not create device nodes.
> 
> Here is the partition table from fdisk, fdisk does run fine.. its just
> the fact this node is not created that threw me off before.
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1   *           1           2       16033+   0  Empty
> /dev/sdb2   *           6        2431    19486845    b  W95 FAT32
> /dev/sdb3               3           5       24097+  83  Linux
> 
> 
> Notice, /dev/sdb1 is a Empty partition... in /dev I only have sdb,
> sdb2, and sdb3.  No sdb1.  Any help would be appreciated.

Looks like it might be a scsi issue.  Redirecting to that mailing list
now.  Anyone here have a clue?

thanks,

greg k-h

       reply	other threads:[~2005-05-03  3:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d4757e6005050219514ece0c0a@mail.gmail.com>
2005-05-03  3:14 ` Greg KH [this message]
2005-05-03  3:26   ` Empty partition nodes not created (was device node issues with recent mm's and udev) Randy.Dunlap
2005-05-03  4:18     ` Joe
2005-05-03  5:16       ` Randy.Dunlap
2005-05-06  8:04       ` Andries Brouwer
2005-05-06 16:43         ` Bryan Henderson
2005-05-03 10:55     ` Paulo Marques
2005-05-03 23:34       ` Joe
2005-05-06  8:00     ` Andries Brouwer
2005-05-06  8:10       ` Chris Wright
2005-05-06  8:43         ` Andries Brouwer
2005-05-06  9:05           ` Andrew Morton
2005-05-06 14:12             ` James Bottomley
2005-05-06 14:26               ` David Woodhouse
2005-05-06 14:34               ` Kay Sievers
2005-05-06 14:18             ` Kay Sievers
2005-05-06 15:50         ` Greg KH
2005-05-06  7:58   ` Andries Brouwer
     [not found] <3ZVNP-5cq-7@gated-at.bofh.it>
     [not found] ` <E1DTAgo-0002uD-F0@be1.7eggert.dyndns.org>
2005-05-04  3:49   ` Joe
2005-05-04  4:47     ` Grant Coady
2005-05-04 11:42     ` Bodo Eggert

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=20050503031421.GA528@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=joecool1029@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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