From: Petr Rockai <prockai@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] handle transient errors in lvconvert --repair
Date: Wed, 19 May 2010 20:31:34 +0200 [thread overview]
Message-ID: <874oi34ubd.fsf@twilight.int.mornfall.net.> (raw)
In-Reply-To: <4BF3FE5C.8070906@redhat.com> (Takahiro Yasui's message of "Wed, 19 May 2010 11:06:04 -0400")
Hi again,
Takahiro Yasui <tyasui@redhat.com> writes:
> 3. run 'lvconvert --repair'
>
> # lvconvert --config devices{ignore_suspended_devices=1} --repair --use-policies vg00/lv00
> Mirrored transient status: "2 253:1 253:2 24/24 1 AA 3 disk 253:0 D"
> Mirror log status: 1 of 1 images failed - switching to core
> WARNING: Failed to replace 1 of 1 logs in volume lv00
>
> 4. check logical volumes
>
> # lvs
> LV VG Attr LSize Origin Snap% Move Log Copy% Convert
> lv00 vg00 mwi-a- 12.00M 100.00
> lv00_mlog vg00 -wi--- 4.00M
I have tracked the problem down to a silly branching bug in
lvconvert.c. The LV was only being written to disk if mirrors changed,
or log re-allocation was attempted. I have fixed that, and also added
both mine and your testcases to the suite.
The attached patch is on top of the previous one -- it should apply
cleanly on top of current CVS + the lvconvert-repair-transient.diff I
have sent previously. It also fixes a bug in messages, where it would
claim that it failed to replace things even if it never tried to in the
first place.
Please test and let me know if you run into any other issues.
Thanks,
Petr.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvconvert-repair-transient-inter.diff
Type: text/x-diff
Size: 5799 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20100519/e6a38379/attachment.bin>
next prev parent reply other threads:[~2010-05-19 18: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 [this message]
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
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=874oi34ubd.fsf@twilight.int.mornfall.net. \
--to=prockai@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.