From: Bill Davidsen <davidsen@tmr.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Neil Brown <neilb@suse.de>, Luca Berra <bluca@comedia.it>,
linux-raid@vger.kernel.org
Subject: Re: issue with internal bitmaps
Date: Tue, 18 Jul 2006 09:34:35 -0400 [thread overview]
Message-ID: <44BCE36B.1040500@tmr.com> (raw)
In-Reply-To: <44BBDC93.6050603@tmr.com>
Bill Davidsen wrote:
> Neil Brown wrote:
>
>> On Thursday July 6, bluca@comedia.it wrote:
>>
>>
>>> hello, i just realized that internal bitmaps do not seem to work
>>> anymore.
>>>
>>
>>
>> I cannot imagine why. Nothing you have listed show anything wrong
>> with md...
>>
>> Maybe you were expecting
>> mdadm -X /dev/md100
>> to do something useful. Like -E, -X must be applied to a component
>> device. Try
>> mdadm -X /dev/sda1
>>
> To take this from the other end, why should -X apply to a component?
> Since the components can and do change names, and you frequently
> mention assembly by UUID, why aren't the component names determined
> from the invariant array name when mdadm wants them, instead of having
> a user or script check the array to get the components?
Boy, I didn't say that well... what I meant to suggest is that when -E
or -X are applied to the array as a whole, would it not be useful to
itterate them over all of the components rather than than looking for
non-existant data in the array itself?
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-07-18 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 14:12 issue with internal bitmaps Luca Berra
2006-07-06 22:16 ` Neil Brown
2006-07-07 8:29 ` Luca Berra
2006-07-17 18:53 ` Bill Davidsen
2006-07-18 13:34 ` Bill Davidsen [this message]
2006-07-18 22:54 ` Luca Berra
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=44BCE36B.1040500@tmr.com \
--to=davidsen@tmr.com \
--cc=bluca@comedia.it \
--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 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.