From: Jonathan E Brassow <jbrassow@redhat.com>
To: Kergon Alasdair <agk@redhat.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: mirroring: [patch 5 of 6] device failure tolerance
Date: Thu, 30 Jun 2005 13:10:04 -0500 [thread overview]
Message-ID: <81d8053f082764c89f295d2defd3e16c@redhat.com> (raw)
In-Reply-To: <20050630175645.GG27078@agk.surrey.redhat.com>
On Jun 30, 2005, at 12:56 PM, Alasdair G Kergon wrote:
> On Thu, Jun 30, 2005 at 11:38:28AM -0500, Kevin Corry wrote:
>> Any time a target's table-format or status-format changes, we also
>> need to
>> increment that target's version number so user-space can figure out
>> which
>> format to expect.
>
> Indeed, but I don't want version numbers updating till we know what
> sequence things will go upstream.
>
> BTW I've not seen a justification for breaking the existing format here
> yet as opposed to simply appending new data to the end of the status
> line.
>
mirror_status first calls the log status function and then adds on to
that. If we want to do what you are proposing, we would move the log
status function _after_ the DMEMIT's for mirror and it would only print
out a char for each log device indicating status. We would have to
remember that STATUSTYPE_INFO and STATUSTYPE_TABLE would call the log
status function at different place (one after it's own DMEMITs, the
other before).
brassow
next prev parent reply other threads:[~2005-06-30 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 8:00 mirroring: [patch 5 of 6] device failure tolerance Jonathan E Brassow
2005-06-30 16:38 ` Kevin Corry
2005-06-30 17:56 ` Alasdair G Kergon
2005-06-30 18:00 ` Kevin Corry
2005-06-30 18:10 ` Jonathan E Brassow [this message]
2005-06-30 18:58 ` Alasdair G Kergon
2005-06-30 19:05 ` Jonathan E Brassow
2005-06-30 19:51 ` Alasdair G Kergon
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=81d8053f082764c89f295d2defd3e16c@redhat.com \
--to=jbrassow@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.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 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.