From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Sanjana <sanjana.linux@gmail.com>
Subject: Re: Cannot mount underlying block device after creating dm device.
Date: Thu, 03 Nov 2011 15:05:19 -0400 [thread overview]
Message-ID: <4EB2E5EF.6010207@cfl.rr.com> (raw)
In-Reply-To: <CABMcfaMi_FpOhG2g2vjxCOA8e89Bd+8UGSq0mCb0e+mfeocLeQ@mail.gmail.com>
On 11/2/2011 11:18 PM, Sanjana wrote:
> [root@bladelinux01 ~]# mount /dev/loop0 /mnt/
> mount: /dev/loop0 already mounted or /mnt/ busy
> [root@bladelinux01 ~]# mount /dev/loop1 /mnt/
> mount: /dev/loop1 already mounted or /mnt/ busy
>
> But if I remove the dm device created and try to mount the underlying
> block-device, I can mount both the device which took part in mirroring and
> I can access the data in both the disk.
> [root@bladelinux01 ~]# dmsetup remove raid1
> [root@bladelinux01 ~]# mount /dev/loop0 /mnt/
> [root@bladelinux01 ~]# ls -l /mnt/
> total 51
> drwx------. 2 root root 12288 Nov 2 22:32 lost+found
> -rw-------. 1 root root 37417 Nov 2 22:38 messages
>
> [root@bladelinux01 ~]# umount /mnt/
> [root@bladelinux01 ~]# mount /dev/loop1 /mnt/
> [root@bladelinux01 ~]# ls -l /mnt/
> total 51
> drwx------. 2 root root 12288 Nov 2 22:32 lost+found
> -rw-------. 1 root root 37417 Nov 2 22:38 messages
>
> Why is this behavior. any explanation, please....
Simple; the loop devices are still open by device-mapper, so mount is
telling you they are busy. Just because the raid device has zero opens
does not mean that it closes the underlying devices.
prev parent reply other threads:[~2011-11-03 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 3:18 Cannot mount underlying block device after creating dm device Sanjana
2011-11-03 19:05 ` Phillip Susi [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=4EB2E5EF.6010207@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dm-devel@redhat.com \
--cc=sanjana.linux@gmail.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.