* New disk under /dev/mapper control??
@ 2007-04-09 21:29 Paul Tader
2007-04-10 5:25 ` Luca Berra
0 siblings, 1 reply; 3+ messages in thread
From: Paul Tader @ 2007-04-09 21:29 UTC (permalink / raw)
To: dm-devel
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: New disk under /dev/mapper control??
2007-04-09 21:29 New disk under /dev/mapper control?? Paul Tader
@ 2007-04-10 5:25 ` Luca Berra
2007-04-10 15:01 ` New disk under /dev/mapper control?? [RESOLVED] Paul Tader
0 siblings, 1 reply; 3+ messages in thread
From: Luca Berra @ 2007-04-10 5:25 UTC (permalink / raw)
To: dm-devel
On Mon, Apr 09, 2007 at 04:29:26PM -0500, Paul Tader wrote:
>I've added a new, single IDE disk to a system. I've run though fdisk,
It does not look "new" to me...
>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?
it is not device mapper, but dmraid
i believe your ide disk was 'touched' by a promise fakeraid controller.
your init scripts probably call dmraid during boot and finding a promise
fakeraid metadata on the disk dmraid activates it.
>I've tried removing and clearing the devices with dmsetup, all to no avail.
you could try removing the fakeraid metadata with dmraid -E.
if the promise fakeraid adapter is installed in your PC you might have
to disable fakeraid in the bios first.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: New disk under /dev/mapper control?? [RESOLVED]
2007-04-10 5:25 ` Luca Berra
@ 2007-04-10 15:01 ` Paul Tader
0 siblings, 0 replies; 3+ messages in thread
From: Paul Tader @ 2007-04-10 15:01 UTC (permalink / raw)
To: dm-devel
> On Mon, Apr 09, 2007 at 04:29:26PM -0500, Paul Tader wrote:
>>I've added a new, single IDE disk to a system. I've run though fdisk,
> It does not look "new" to me...
>
>>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?
> it is not device mapper, but dmraid
> i believe your ide disk was 'touched' by a promise fakeraid controller.
> your init scripts probably call dmraid during boot and finding a promise
> fakeraid metadata on the disk dmraid activates it.
>
>>I've tried removing and clearing the devices with dmsetup, all to no
>> avail.
> you could try removing the fakeraid metadata with dmraid -E.
> if the promise fakeraid adapter is installed in your PC you might have
> to disable fakeraid in the bios first.
>
Thanks Luca, the dmraid command corrected things.
[root@server ~]# dmraid -r
/dev/hdb: pdc, "pdc_bjajcgbifh", stripe, ok, 781422592 sectors, data@ 0
[root@server ~]# dmraid -rE
Do you really want to erase "pdc" ondisk metadata on /dev/hdb ? [y/n] :y
...then I ran:
[root@server ~]# dmsetup remove /dev/mapper/pdc_bjajcgbifh1
[root@server ~]# dmsetup remove /dev/mapper/pdc_bjajcgbifh
and rebooted. This time the /dev/mapper devices were not recreated and I
was able to mount the partition using the standard device file, /dev/hdb1.
Thanks again,
Paul Tader
--
www.linuxscope.com
> L.
>
> --
> Luca Berra -- bluca@comedia.it
> Communication Media & Services S.r.l.
> /"\
> \ / ASCII RIBBON CAMPAIGN
> X AGAINST HTML MAIL
> / \
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-04-10 15:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-04-09 21:29 New disk under /dev/mapper control?? Paul Tader
2007-04-10 5:25 ` Luca Berra
2007-04-10 15:01 ` New disk under /dev/mapper control?? [RESOLVED] Paul Tader
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.