From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] md: register new md sysfs file 'uuid' read-only
Date: Tue, 09 Oct 2012 10:54:37 +0200 [thread overview]
Message-ID: <5073E64D.2020506@profitbricks.com> (raw)
In-Reply-To: <20121009140248.3ad91484@notabene.brown>
On 09.10.2012 05:02, NeilBrown wrote:
> Kernel sometimes knows. Some arrays have metadata handled by user-space so
> the kernel wouldn't be able to report anything.
> Userspace always knows..
Thanks for the hint. I didn't think about that.
> 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?
Thanks for the hint. Our 3.2.5-Version didn't build it for an existing
location. I made it do so but I don't like the UUID format in there.
I assembled UUID 12345678:12345678:12345678:12345678 and the file
contains the following:
md0 1.2 78563412:78563412:78563412:78563412 /dev/md0
This would be a nice file if I could grep for the UUID in the same
format as I've entered it upon creation/assembly.
So, I guess we can live with a custom patch for now and close the
discussion here.
>> 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.
I'll open a new topic for this after analysing it in more detail today.
I've only seen the issue on the PC of my boss and some automation guys
reported it.
Cheers,
Sebastian
prev parent reply other threads:[~2012-10-09 8:54 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
2012-10-09 8:54 ` Sebastian Riemer [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=5073E64D.2020506@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).