From: NeilBrown <neilb@suse.de>
To: Oleg Samarin <osamarin68@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: How does linux hide underlying disks partitions?
Date: Sat, 30 May 2015 07:14:26 +1000 [thread overview]
Message-ID: <20150530071426.75a7302e@notabene.brown> (raw)
In-Reply-To: <1432926434.4733.1.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
On Fri, 29 May 2015 22:07:14 +0300 Oleg Samarin <osamarin68@gmail.com> wrote:
> I'm trying to evaluate a complex mdadm-lvm-udev-anaconda issue
> https://bugzilla.redhat.com/show_bug.cgi?id=1226305 and to undestand
> how mdadm works.
>
> I have an intel imsm raid-1 volume /dev/md126 assembled with two
> disks /dev/sda and /dev/sdb.
> This volume has two partitions /dev/md126p1 and /dev/md126p2.
>
> Because it a simple mirror, both disks have te same information.
>
> When the normal system boots up, I can see with journalctl that
>
> 1. at first /dev/sda1, /dev/sda2, /dev/sdb1, /dev/sdb2 appear
> 2. then mdadm assembles /dev/md126 from /dev/sda and /dev/sdb
> 3. /dev/sda1, /dev/sda2, /dev/sdb1, /dev/sdb2 disappear
> 4. /dev/md126p1 and /dev/md126p2 coming instead
>
> Which program component is responsible for
> disappearing /dev/sda1, /dev/sda2, /dev/sdb1 and /dev/sdb2?
mdadm has a function "remove_partitions" which uses the BLKPG ioctl to tell
the kernel to forget about the partitions.
>
> Why can they be left after starting anaconda installer?
I don't know anything about anaconda - maybe someone else can help.
NeilBrown
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2015-05-29 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 19:07 How does linux hide underlying disks partitions? Oleg Samarin
2015-05-29 21:14 ` NeilBrown [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=20150530071426.75a7302e@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=osamarin68@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.