From: Paulo Marques <pmarques@grupopie.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Greg KH <greg@kroah.com>,
joecool1029@gmail.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
Date: Tue, 03 May 2005 11:55:56 +0100 [thread overview]
Message-ID: <427758BC.1090906@grupopie.com> (raw)
In-Reply-To: <20050502202620.04467bbd.rddunlap@osdl.org>
Randy.Dunlap wrote:
> On Mon, 2 May 2005 20:14:21 -0700 Greg KH wrote:
>
> | 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?
>
> Could this 2.6.11.8 -stable patch fix it?
> Subject: [04/07] partitions/msdos.c fix
>
> Joe, can you test 2.6.11.8, please?
It seems to me that this exactly the other way around. The patch is
probably already in -mm and is doing what it is supposed to do: don't
report partitions whose system ID == 0.
Can you try to give the empty partition a type different than zero? You
don't need to make a file system on it or anything, just change the type.
Or check if the patch Randy is pointing to is already in your tree and
revert it.
I think this is a good argument not to include this patch on the -stable
release...
--
Paulo Marques - www.grupopie.com
All that is necessary for the triumph of evil is that good men do nothing.
Edmund Burke (1729 - 1797)
next prev parent reply other threads:[~2005-05-03 10:56 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 ` Empty partition nodes not created (was device node issues with recent mm's and udev) Greg KH
2005-05-03 3:26 ` 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 [this message]
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=427758BC.1090906@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=joecool1029@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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