From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l4LEIDqZ032428 for ; Mon, 21 May 2007 10:18:13 -0400 Received: from web38214.mail.mud.yahoo.com (web38214.mail.mud.yahoo.com [209.191.124.157]) by mx3.redhat.com (8.13.1/8.13.1) with SMTP id l4LEICVC009766 for ; Mon, 21 May 2007 10:18:12 -0400 Date: Mon, 21 May 2007 07:18:00 -0700 (PDT) From: Sean McGlynn MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1778335099-1179757080=:80102" Message-ID: <247618.80102.qm@web38214.mail.mud.yahoo.com> Subject: [linux-lvm] Disk /dev/dm-0 doesn't contain a valid partition table Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development --0-1778335099-1179757080=:80102 Content-Type: text/plain; charset=ascii Hello, I did an fdisk -l to review my partition table (see results below), and found four entries that end with "Disk /dev/dm-X doesn't contain a valid partition table." I don't recall seeing this in the past, so I believe it is something new. I recently began using kernel 2.6.21.1, up from 2.6.9-42. I don't know if perhaps this had some effect, or if the entries are normal and I just never noticed them. What led me here is that sar -d output includes four entries for hard drives (dev253 entries) when there are only three on my system. Fdisk is reporting four DM devices, so I'm thinking there is some correlation, but I don't know what. Any constructrive feedback would be appreciated. Thank you. Disk /dev/sda: 1900.1 GB, 1900120375296 bytes 255 heads, 63 sectors/track, 231009 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 231009 1855579761 8e Linux LVM Disk /dev/sdb: 146.1 GB, 146163105792 bytes 255 heads, 63 sectors/track, 17769 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 38 305203+ 83 Linux /dev/sdb2 39 17769 142424257+ 8e Linux LVM Disk /dev/sdc: 146.1 GB, 146163105792 bytes 255 heads, 63 sectors/track, 17769 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 1 17769 142729461 8e Linux LVM Disk /dev/dm-0: 137.4 GB, 137405399040 bytes 255 heads, 63 sectors/track, 16705 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 8388 MB, 8388608000 bytes 255 heads, 63 sectors/track, 1019 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 146.1 GB, 146150522880 bytes 255 heads, 63 sectors/track, 17768 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-2 doesn't contain a valid partition table Disk /dev/dm-3: 1900.1 GB, 1900111986688 bytes 255 heads, 63 sectors/track, 231008 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-3 doesn't contain a valid partition table ____________________________________________________________________________________Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 --0-1778335099-1179757080=:80102 Content-Type: text/html; charset=ascii

Hello,

 

I did an fdisk -l to review my partition table (see results below), and found four entries that end with "Disk /dev/dm-X doesn't contain a valid partition table."  I don't recall seeing this in the past, so I believe it is something new.

 

I recently began using kernel 2.6.21.1, up from 2.6.9-42.  I don't know if perhaps this had some effect, or if the entries are normal and I just never noticed them.

 

What led me here is that sar -d output includes four entries for hard drives (dev253 entries) when there are only three on my system.  Fdisk is reporting four DM devices, so I'm thinking there is some correlation, but I don't know what.

 

Any constructrive feedback would be appreciated.

 

Thank you.


Disk /dev/sda: 1900.1 GB, 1900120375296 bytes
255 heads, 63 sectors/track, 231009 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1      231009  1855579761   8e  Linux LVM

 

Disk /dev/sdb: 146.1 GB, 146163105792 bytes
255 heads, 63 sectors/track, 17769 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          38      305203+  83  Linux
/dev/sdb2              39       17769   142424257+  8e  Linux LVM

 

Disk /dev/sdc: 146.1 GB, 146163105792 bytes
255 heads, 63 sectors/track, 17769 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       17769   142729461   8e  Linux LVM

 

Disk /dev/dm-0: 137.4 GB, 137405399040 bytes
255 heads, 63 sectors/track, 16705 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

 

Disk /dev/dm-1: 8388 MB, 8388608000 bytes
255 heads, 63 sectors/track, 1019 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

 

Disk /dev/dm-2: 146.1 GB, 146150522880 bytes
255 heads, 63 sectors/track, 17768 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-2 doesn't contain a valid partition table

 

Disk /dev/dm-3: 1900.1 GB, 1900111986688 bytes
255 heads, 63 sectors/track, 231008 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-3 doesn't contain a valid partition table


Pinpoint customers who are looking for what you sell. --0-1778335099-1179757080=:80102--