From: martin f krafft <madduck@madduck.net>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nested block devices (partitioned RAID with LVM): where Linux sucks ;-)
Date: Wed, 29 Jun 2011 11:40:18 +0200 [thread overview]
Message-ID: <20110629094017.GA12692@albatross.gern.madduck.net> (raw)
In-Reply-To: <4E0AED02020000A100006458@gwsmtp1.uni-regensburg.de>
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
also sprach Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> [2011.06.29.0914 +0200]:
> 1) The original error message of mdadm about a wrong UUID is
> completely wrong ("device busy" would have been correct)
Correct. It would be nice if you could file a bug about this in your
distro's bug tracker (or Debian's).
> 2) partitions on unassembled raid legs are activated before the
> RAID is assembled, effectively preventing a RAID assembly (I could
> not find out how to fix/prevent this)
I think you will find that LVM snatched the PV before mdadm had
a chance, hence it was busy. This is a common problem with LVM and
RAID1, because LVM (also) scans all devices and because RAID1 is
merely a mirroring setup, LVM can use either of the components just
as well.
The solution? I thought that there was a patch to LVM that prevented
it from using RAID members. But if there isn't, then exclude the
devices from its scan.
… and before you claim that Linux sucks, consider how a computer
should do it differently. I think you will find that every
implementation has to make certain hard assumptions (for it lacks
human abstraction and combination abilities), and your current
griefs make you feel like Linux does it worst of all. Rest assured:
it doesn't. It makes assumptions, but you will find that they are
quite sensible.
> I haven't studied the block data structures, but obviously the
> RAID metadata is not at the start of the devices. If they were,
> a partition table would not be found, and the RAID could have been
> assembled without a problem.
You are right, the metadata are not at the start. This is by design.
> I'm sending this message to make developers aware of the problem,
(in which case it might be wise to avoid exclaiming things like
"linux sucks"…)
> P.S. Novell Support was not able to provide a solution for this problem in time
News at 11…
--
martin | http://madduck.net/ | http://two.sentenc.es/
"no, 'eureka' is greek for 'this bath is too hot.'"
-- dr. who
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) --]
[-- Type: application/pgp-signature, Size: 1124 bytes --]
next prev parent reply other threads:[~2011-06-29 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 7:14 Ulrich Windl
2011-06-29 9:40 ` martin f krafft [this message]
2011-06-29 14:43 ` Phil Turmel
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=20110629094017.GA12692@albatross.gern.madduck.net \
--to=madduck@madduck.net \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®