From: Phil Turmel <philip@turmel.org>
To: Sebastian Riemer <sebastian.riemer@profitbricks.com>
Cc: NeilBrown <neilb@suse.de>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] md: register new md sysfs file 'uuid' read-only
Date: Mon, 08 Oct 2012 13:50:53 -0400 [thread overview]
Message-ID: <5073127D.7070500@turmel.org> (raw)
In-Reply-To: <50730010.5090605@profitbricks.com>
On 10/08/2012 12:32 PM, Sebastian Riemer 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.
> "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.
>
> 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.
>
> If you like it better in the xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx format,
> I can resend the patch in that format.
If you are aiming for consistency, the dm driver(s) have already
established a no-punctuation format for the UUID itself (punctuation
separates UUID type from the UUID) within sysfs.
Regards,
Phil
next prev parent reply other threads:[~2012-10-08 17:50 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 [this message]
2012-10-09 3:02 ` NeilBrown
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=5073127D.7070500@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--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).