From: "Paul Tader" <ptader@linuxscope.com>
To: dm-devel@redhat.com
Subject: New disk under /dev/mapper control??
Date: Mon, 9 Apr 2007 16:29:26 -0500 (CDT) [thread overview]
Message-ID: <44864.131.225.80.2.1176154166.squirrel@mail.linuxscope.com> (raw)
I've added a new, single IDE disk to a system. I've run though fdisk,
mkfs and then attempted a mount command but mount failed with "already
mounted or /mnt/ busy". I see that now device-mapper is "claiming" this
disk and newly created partitions and doesn't allow me to mount the
partitions by addressing the /dev/hdb1 device file. In other words,
/dev/mapper files are being automatically created only for this (new)
disk. Is there a way to have device-mapper relinquish control of this
disk?
I've tried removing and clearing the devices with dmsetup, all to no avail.
Thanks much,
Paul
(device files removed and no paritions present on /dev/hdb):
[root@server ~]# ls -l /dev/mapper/
total 0
crw------- 1 root root 10, 63 Apr 9 12:03 control
(after a reboot a new device appears (for the hdb device?))
[root@server ~]# ls -l /dev/mapper/
total 0
crw------- 1 root root 10, 63 Apr 9 15:04 control
brw-rw---- 1 root disk 253, 0 Apr 9 15:04 pdc_bjajcgbifh
(Now fdisk, create a new primary partition, mkfs, and then mount attempted):
[root@server ~]# mount /dev/hdb1 /mnt/
mount: /dev/hdb1 already mounted or /mnt/ busy
(no device for the new partition, yet)
[root@server ~]# ls -l /dev/mapper
total 0
crw------- 1 root root 10, 63 Apr 9 15:04 control
brw-rw---- 1 root disk 253, 0 Apr 9 15:04 pdc_bjajcgbifh
(..but after a reboot, a new mapper device is present)
[root@server ~]# ls -l /dev/mapper
total 0
crw------- 1 root root 10, 63 Apr 9 15:54 control
brw-rw---- 1 root disk 253, 0 Apr 9 15:54 pdc_bjajcgbifh
brw-rw---- 1 root disk 253, 1 Apr 9 15:54 pdc_bjajcgbifh1
(still can't mount using traditional device)
[root@server ~]# mount /dev/hdb1 /mnt/
mount: /dev/hdb1 already mounted or /mnt/ busy
(...but can using the special mapper device)
[root@server ~]# mount /dev/mapper/pdc_bjajcgbifh1 /mnt
[root@server ~]# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
...
/dev/mapper/pdc_bjajcgbifh1
23078680 77800 23000880 1% /mnt
-------------------------
Linux 2.6.9-42.0.10.ELsmp #1 SMP Tue Feb 27 12:38:15 EST 2007 x86_64
x86_64 x86_64 GNU/Linux
# rpm -q device-mapper
device-mapper-1.02.07-4.0.RHEL4
device-mapper-1.02.07-4.0.RHEL4
64bit and 32bit RPM's installed.
[root@server ~]# fdisk -l
Disk /dev/hdb: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 2919 23446836 83 Linux
Disk /dev/sda: 120.0 GB, 120033075200 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1044 8385898+ 83 Linux
/dev/sda2 1045 2088 8385930 82 Linux swap
/dev/sda3 2089 3132 8385930 83 Linux
/dev/sda4 3133 14593 92060482+ 5 Extended
/dev/sda5 3133 3654 4192933+ 83 Linux
/dev/sda6 3655 4176 4192933+ 83 Linux
next reply other threads:[~2007-04-09 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 21:29 Paul Tader [this message]
2007-04-10 5:25 ` New disk under /dev/mapper control?? Luca Berra
2007-04-10 15:01 ` New disk under /dev/mapper control?? [RESOLVED] Paul Tader
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=44864.131.225.80.2.1176154166.squirrel@mail.linuxscope.com \
--to=ptader@linuxscope.com \
--cc=dm-devel@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.