Re: Empty partition nodes not created (was device node issues withrecent mm's and udev)

[Paulo Marques]

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)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/