From: David Teigland <teigland@redhat.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] new releases with important bug fix
Date: Wed, 31 Oct 2018 15:13:14 -0500 [thread overview]
Message-ID: <20181031201314.GC14722@redhat.com> (raw)
Two new releases are available:
2.02.182 (from the stable branch)
https://sourceware.org/git/?p=lvm2.git;a=tag;h=d64377b5bbd2d170f1d6365157e2245d90a63c1a
2.03.01 (from the development branch)
https://sourceware.org/git/?p=lvm2.git;a=tag;h=1326762567c49c7305d83ac59dff819d7de964fd
These releases fix a bug that can potentially cause data corruption in a
rare situation described below. The bug first appeared in version
2.02.178 (June 2018). The subject of the fix is "metadata: prevent
writing beyond metadata area".
Bug details:
Most VGs will not be affected by this bug. It can only happen when the
first physical extent (PE) in the VG is unaligned with 128KB. By default
the first PE is at 1MB, so any VG using the default will be immune. To
check the first PE offset, run:
$ vgs -o+pe_start --units k <vgname>
If the 1st PE field is 1024 KB, or another multiple of 128KB, then the VG
will be unaffected.
In cases where a command line or config option was used to create a VG
with an unaligned first PE, then the bug can potentially arise when:
1. An lvm command is being run and is updating the VG metadata,
e.g. lvcreate, lvextend, vgextend.
2. The VG metadata is being updated at the tail end of the circular
metadata buffer on disk.
3. A program (or file system) is writing changes to the 128KB of data
that follows the lvm metadata, at the same time that lvm is writing
its metadata.
Given this specific combination of updates, lvm could "undo" the change
made by the program/fs (lvm reads X, program writes X+1, lvm writes X.)
Apart from updating to a fixed version of lvm, the best way to avoid any
possible problem (in an unaligned VG) is to avoid running lvm commands
that change metadata while LVs in the VG are being used.
reply other threads:[~2018-10-31 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181031201314.GC14722@redhat.com \
--to=teigland@redhat.com \
--cc=linux-lvm@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 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).