On Wed, Jun 19, 2002 at 10:02:48AM +0100, Dave Jones wrote:
> I got a bug report about an issue with LVM in 2.5.22-dj1, which turns
> out to be caused by broken /proc/partitions in mainline.
>
> (davej@mesh:davej)$ cat /proc/partitions
> major minor #blocks name
>
> 8 0 0 sda
> 22 0 1515870810 hdc
> 22 64 1515870810 hdd
> 3 0 29316672 hda
> 3 1 117400 hda1
> 3 2 1 hda2
> 3 5 999904 hda5
> 3 6 1499872 hda6
> 3 7 683392 hda7
> 3 8 26015944 hda8
> 3 64 1515870810 hdb
>
> Note the huge numbers in hex are 0x5a5a5a5a, so something
> seems to be getting poisoned somewhere.
>
> Also, should partitions with 0 blocks be showing up ?
> I don't recall that happening with the old-style 2.4 code.
I changed something here a few weeks ago. The idea was to avoid
listing partitions of size 0 but do list full devices, regardless
of size. Especially in case of removable media that is useful.
For example, a
blockdev --rereadpt /dev/sda
might show that there is something there now.
Will look at what might cause your strange numbers. Unfortunately
recent 2.5 kernels do not boot for me.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 23 2002 - 22:00:19 EST