From: NeilBrown <neilb@suse.de>
To: Sebastian Riemer <sebastian.riemer@profitbricks.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] md: register new md sysfs file 'uuid' read-only
Date: Tue, 9 Oct 2012 14:02:48 +1100 [thread overview]
Message-ID: <20121009140248.3ad91484@notabene.brown> (raw)
In-Reply-To: <50730010.5090605@profitbricks.com>
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
On Mon, 08 Oct 2012 18:32:16 +0200 Sebastian Riemer
<sebastian.riemer@profitbricks.com> wrote:
> Hi Neil,
>
> I must have overseen your answer. We want to use as less mdadm as
> possible - especially for simple checking stuff. The kernel knows best.
Kernel sometimes knows. Some arrays have metadata handled by user-space so
the kernel wouldn't be able to report anything.
Userspace always knows..
> "mdadm -D" reads the data from disk. This means additional disk access.
> It is also possible that this command triggers superblock updates.
> Simple checking stuff shouldn't have to use disk access.
In that case, how about using /run/mdadm/map ??
When mdadm assembles an array it needs to know the uuid, and it records this
in that file for future reference. Will that do?
>
> We are planning to use MD RAID a little bit different with e.g. 100 MD
> arrays. Searching for a particular UUID in this bunch of MD devices can
> be difficult without this patch. This is how the kernel represents
> UUIDs. Conversion can be done in user space.
I believe that format is for RFC4122 UUIDs. MD's UUIDs are not created
according to those rules, so it isn't really appropriate to make it look like
they were.
However the formatting isn't the big issue - the UUID is something the kernel
knows by accident more than by necessity. I'd rather it didn't.
>
> If you like it better in the xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx format,
> I can resend the patch in that format.
>
> It simplifies our checking magic not to rely on udev symlinks and to ask
> the kernel for the cached UUID.
>
> Btw.: We did an "Assemble-Resize-Stop, Assemble-Resize-Stop, ..."-Test
> with "--assume-clean" and the second resize doesn't work. With
> "Assemble-Resize-Detail-Stop" it works.
More details? What exactly do you mean by "Resize"? What exactly do you
mean by "doesn't work"? Can you make a simple script that reproduces this?
If so, I'd love to see it.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-10-09 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 13:42 [PATCH] md: register new md sysfs file 'uuid' read-only Sebastian Riemer
2012-10-02 22:30 ` NeilBrown
2012-10-08 16:32 ` Sebastian Riemer
2012-10-08 17:50 ` Phil Turmel
2012-10-09 3:02 ` NeilBrown [this message]
2012-10-09 8:54 ` Sebastian Riemer
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=20121009140248.3ad91484@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=sebastian.riemer@profitbricks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).