From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: issue with internal bitmaps
Date: Wed, 19 Jul 2006 00:54:29 +0200 [thread overview]
Message-ID: <20060718225429.GB28146@percy.comedia.it> (raw)
In-Reply-To: <44BCE36B.1040500@tmr.com>
On Tue, Jul 18, 2006 at 09:34:35AM -0400, Bill Davidsen wrote:
>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?
the question i believe is to distinguish the case where an md device is
a component of another md device...
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
prev parent reply other threads:[~2006-07-18 22:54 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
2006-07-18 22:54 ` Luca Berra [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=20060718225429.GB28146@percy.comedia.it \
--to=bluca@comedia.it \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).