Bug 708444 - snapshot extension operations are reported even when the threshold is turned off
Summary: snapshot extension operations are reported even when the threshold is turned off
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2
Version: 5.7
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Petr Rockai
QA Contact: Corey Marthaler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-27 16:20 UTC by Corey Marthaler
Modified: 2012-02-21 06:04 UTC (History)
9 users (show)

Fixed In Version: lvm2-2.02.88-2.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-21 06:04:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0161 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2012-02-20 15:07:59 UTC

Description Corey Marthaler 2011-05-27 16:20:36 UTC
Description of problem:
Even with the threshold turned off, lvm still reports automatic extension of volumes when they are being written to and filling up.

    # Setting snapshot_autoextend_threshold to 100 disables automatic
    # extensions. The minimum value is 50 (A setting below 50 will be treated
    # as 50).

    snapshot_autoextend_threshold = 100
    snapshot_autoextend_percent = 20

[root@taft-01 ~]# lvs -a -o +devices
 LV      VG        Attr   LSize   Origin Snap%  Devices
 origin  snapper   owi-a- 300.00M               /dev/sdh1(0)
 snap1   snapper   swi-a-  52.00M origin 84.85  /dev/sdh1(75)

From log:
May 27 11:08:12 taft-01 lvm[7319]: Extension of snapshot snapper/snap1 finished successfully.
May 27 11:08:42 taft-01 last message repeated 3 times
May 27 11:08:52 taft-01 lvm[7319]: Snapshot snapper-snap1 is now 81% full.
May 27 11:08:52 taft-01 lvm[7319]: Extension of snapshot snapper/snap1 finished successfully.


Version-Release number of selected component (if applicable):
2.6.18-261.el5

lvm2-2.02.84-3.el5    BUILT: Wed Apr 27 03:42:24 CDT 2011
lvm2-cluster-2.02.84-3.el5    BUILT: Wed Apr 27 03:42:43 CDT 2011
device-mapper-1.02.63-3.el5    BUILT: Thu May 19 08:09:22 CDT 2011
device-mapper-event-1.02.63-3.el5    BUILT: Thu May 19 08:09:22 CDT 2011
cmirror-1.1.39-10.el5    BUILT: Wed Sep  8 16:32:05 CDT 2010
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009


How reproducible:
Everytime

Comment 4 Petr Rockai 2011-10-19 14:42:13 UTC
I have removed the message altogether, as it is redundant nowadays (LVM command in question reports everything relevant already).

Comment 5 Milan Broz 2011-10-21 15:14:16 UTC
Fixed in lvm2-2.02.88-2.el5.

Comment 7 Corey Marthaler 2011-11-17 22:33:47 UTC
"Extension of snapshot $snap finished successfully" messages are no longer reported at all, even when threshold is turned on. Marking verified.

Nov 17 16:16:08 hayes-01 lvm[7344]: Monitoring snapshot snapper-auto_extension 
Nov 17 16:16:18 hayes-01 lvm[7344]: Extending logical volume auto_extension to 120.00 MB
Nov 17 16:16:18 hayes-01 lvm[7344]: Logical volume auto_extension successfully resized
Nov 17 16:23:33 hayes-01 lvm[7344]: No longer monitoring snapshot snapper-auto_extension 
Nov 17 16:25:02 hayes-01 lvm[7344]: Monitoring snapshot snapper-auto_extension 
Nov 17 16:25:12 hayes-01 lvm[7344]: Extending logical volume auto_extension to 120.00 MB
Nov 17 16:25:12 hayes-01 lvm[7344]: Logical volume auto_extension successfully resized
Nov 17 16:25:20 hayes-01 lvm[7344]: No longer monitoring snapshot snapper-auto_extension 


2.6.18-274.el5

lvm2-2.02.88-4.el5    BUILT: Wed Nov 16 09:40:55 CST 2011
lvm2-cluster-2.02.88-4.el5    BUILT: Wed Nov 16 09:46:51 CST 2011
device-mapper-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
device-mapper-event-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
cmirror-1.1.39-10.el5    BUILT: Wed Sep  8 16:32:05 CDT 2010
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009

Comment 8 errata-xmlrpc 2012-02-21 06:04:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0161.html


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