All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Disk /dev/dm-0 doesn't contain a valid partition table
Date: Mon, 21 May 2007 15:28:35 +0100	[thread overview]
Message-ID: <4651AC93.8090309@redhat.com> (raw)
In-Reply-To: <247618.80102.qm@web38214.mail.mud.yahoo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sean McGlynn wrote:
> 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.

Later kernels include dm devices in the list of partitions in proc, so
fdisk will attempt to scan them for partition tables. It's not harmful,
just noise.

> 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.

If you don't like it & you've not configured anything to use /dev/dm-*
devices directly (instead of /dev/mapper/* or /dev/<volgroup>/* or
whatever) then you can reconfigure udev to not create the dm-* nodes.

- From memory, you need to comment out the rule that begins
"KERNEL="dm-[0-9]*" in /etc/udev/rules.d/50-udev.rules, or, for newer
udevs you can add ignore_device:

KERNEL=="dm-[0-9]*", ACTION=="add", OPTIONS+="ignore_device"

>  
> 
> 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.

Those "dev253" entries are your device-mapper devices. Take a look at
/dev/dm-* with ls -l and you will see that the major number is 253.

Kind regards,
Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGUayT6YSQoMYUY94RAqJKAJ9dFJtaRg3fONo7kLOkDezcS/FizwCcDwFj
2McvW5Wl+zudmUZDO2aE1fQ=
=NHOE
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-05-21 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 14:18 [linux-lvm] Disk /dev/dm-0 doesn't contain a valid partition table Sean McGlynn
2007-05-21 14:28 ` Bryn M. Reeves [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-21 15:16 Sean McGlynn
2007-05-21 15:44 ` Bryn M. Reeves
2007-05-21 16:02 Sean McGlynn

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=4651AC93.8090309@redhat.com \
    --to=breeves@redhat.com \
    --cc=linux-lvm@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.