Bug 1132512 - Thin pool incorrectly updates transaction_id when it is skipped via volume_list
Summary: Thin pool incorrectly updates transaction_id when it is skipped via volume_list
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Zdenek Kabelac
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 1132547
TreeView+ depends on / blocked
Reported: 2014-08-21 13:37 UTC by bjs
Modified: 2014-08-27 07:40 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1132547 (view as bug list)
Last Closed: 2014-08-27 07:40:12 UTC
Type: Bug

Attachments (Terms of Use)

Description bjs 2014-08-21 13:37:35 UTC
First I created the physical volume, the volume group, one thin pool that almost used all the space of the volume group. Then I created and formated one thinly provisioned volume within this volume group. About a week later my PC had a power failure and was not shutdown cleanly. About two weeks later I opened the luks container and created a new thin volume. I tried to activate it, but I got the following error message.

Thin pool transaction_id=5, while expected: 6.

So the creation of the volume was successful, but the activation wasn't. I had to activate it manually because the name of the volume group was not listed in the "activation" "volume_list" in lvm.conf during the creation of the volume.

The volume group only has one physical volume on a luks encrypted hard drive. The hard drive does not have any partitions. It is a Seagate Barracuda 7200.14 (AF). smartctl does not show any signs of a failure of the hard drive.

Kernel: 3.14.14
LVM version:     2.02.108(2) (2014-07-23)
Library version: 1.02.87 (2014-07-23)
Driver version:  4.27.0

Comment 1 Zdenek Kabelac 2014-08-21 14:03:23 UTC
Yep  tricky one - we miss to really pass messages to thin pools which happens to be skipped because of volume_list.

Comment 2 Zdenek Kabelac 2014-08-26 13:39:12 UTC
Committed upstream fix:


Note You need to log in before you can comment on or make changes to this bug.