archive mirror
 help / color / mirror / Atom feed
From: Eric Ren <>
To: Zdenek Kabelac <>
Cc: LVM general discussion and development <>,, LVM2 development <>
Subject: Re: [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete
Date: Thu, 11 Apr 2019 21:09:14 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


> So do you get  'partial' error on thin-pool activation on your physical server ?

Yes, the VG of the thin pool only has one simple physical disk, at
beginning, I also suspected the disk may disconnect at that moment.
But, I start to think maybe it is caused by some reason hidden in the
interaction between lvm and dm driver in kernel.

It can not be reproduced easily, but happens randomly for several
times. The behavior model of lvm abstracted from the upper service is
there are many (64) control flow in parallel, in each  one it loops to
randomly create/activate/delete thin LVs.

The error happened two place:
1. activate the thin LV:  _lv_activate -> _tree_action ->
dev_manager_activate ->  _add_new_lv_to_dtree -> add_areas_line  ->
striped_add_target_line on **metadata LV**,
I don't what .add_target_line() does for?

2. fail to suspend the origin LV when created.

I'm trying to reproduce it in a simple way, will report once succeed :-)

Thanks very much!

  reply	other threads:[~2019-04-11 13:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  0:27 [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete Eric Ren
2019-04-11 10:01 ` Eric Ren
2019-04-11 11:21   ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-11 11:03 ` [linux-lvm] " Zdenek Kabelac
2019-04-11 11:26   ` Eric Ren
2019-04-11 11:32     ` Zdenek Kabelac
2019-04-11 11:49       ` Eric Ren
2019-04-11 12:12         ` Zdenek Kabelac
2019-04-11 13:09           ` Eric Ren [this message]
2019-04-11 13:13             ` Zdenek Kabelac
     [not found]               ` <>
2019-04-11 17:33                 ` Eric Ren
2019-04-12 10:05                   ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-12 10:42                     ` Eric Ren
2019-04-12 13:44                       ` [linux-lvm] " Zdenek Kabelac

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).