All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] handle transient errors in lvconvert --repair
Date: Wed, 05 May 2010 11:31:51 -0400	[thread overview]
Message-ID: <4BE18F67.9080005@redhat.com> (raw)
In-Reply-To: <87pr1a3i4w.fsf@twilight.int.mornfall.net.>

Hi Petr,

On 05/05/10 03:46, Petr Rockai wrote:
> Takahiro Yasui <tyasui@redhat.com> writes:
>> It is very grad that the patch to fix this issue was being developed.
>> I have not thoroughly read it, but I found one issue. It doesn't work
>> for a "mirrored" log, while it looks good for a "core" or "disk" log.
> [snip]
> 
> this is not really an issue with the new code per se. What needs to be
> done is that lvconvert --repair itself needs to be changed to handle
> mirrored logs correctly.
> 
> What needs to be done is to call the repair recursively on the log
> device if it is a mirror.

I understand. I will wait and test your updated patch.

>> The current code calls lv_check_transient() at the beginning of
>> _lvconvert_mirrors_repair() but I think that lv_check_transient()
>> needs to be called in functions which repairs a mirror log,
>> such as _lv_update_log_type(), too.
> (see above)
> 
>> Also this patch works well not only for a transient error but
>> also a medium error, therefore, function names with '_transient'
>> could be '_status' or '_status_string'. (e.g. lv_check_status())
> I chose transient not because of "transient error", but because of the
> relation to the transient, in-kernel, status of the device -- as opposed
> to persistent, i.e. in metadata. Maybe something with "active" or
> "activation" in it would be better though...

I see your point. I just thought 'a medium error' is persistent
and commented, but I will follow your decision.

Thanks,
Taka



      reply	other threads:[~2010-05-05 15:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 15:14 [PATCH] handle transient errors in lvconvert --repair Petr Rockai
2010-04-27 18:03 ` Petr Rockai
2010-05-06 17:30   ` Petr Rockai
2010-05-14 22:52     ` Takahiro Yasui
2010-05-17 23:01       ` Takahiro Yasui
2010-05-19 12:06         ` Petr Rockai
2010-05-19 15:06           ` Takahiro Yasui
2010-05-19 18:31             ` Petr Rockai
2010-05-19 19:46               ` Takahiro Yasui
2010-05-19 20:19                 ` Petr Rockai
2010-05-19 20:31                   ` Alasdair G Kergon
2010-05-19 20:35                   ` Takahiro Yasui
2010-05-20  0:49               ` Takahiro Yasui
2010-05-20  7:40                 ` Petr Rockai
2010-05-20 11:54                   ` Takahiro Yasui
2010-05-19 16:44           ` Takahiro Yasui
2010-05-19 17:15             ` Takahiro Yasui
2010-05-19 20:26               ` Petr Rockai
2010-04-28 19:37 ` Takahiro Yasui
2010-05-05  7:46   ` Petr Rockai
2010-05-05 15:31     ` Takahiro Yasui [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=4BE18F67.9080005@redhat.com \
    --to=tyasui@redhat.com \
    --cc=lvm-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.