All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Tader" <ptader@linuxscope.com>
To: dm-devel@redhat.com
Subject: Re: New disk under /dev/mapper control?? [RESOLVED]
Date: Tue, 10 Apr 2007 10:01:52 -0500 (CDT)	[thread overview]
Message-ID: <43710.131.225.80.2.1176217312.squirrel@mail.linuxscope.com> (raw)
In-Reply-To: <20070410052536.GA1464@percy.comedia.it>

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

      reply	other threads:[~2007-04-10 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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   ` Paul Tader [this message]

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