[linux-lvm] lvmetad crashes with “memory smash” during lvm parallel operations
David Teigland
teigland at redhat.com
Mon Jul 24 16:58:29 UTC 2017
On Wed, Jul 19, 2017 at 04:57:12AM +0000, Shivarama Krishnan, Gururaj (Nokia - IN/Bangalore) wrote:
> Hi ,
>
> Greetings.
>
> We are facing an issue with LVMETAD crashing during the parallel lvm operations
> (vgscan/pvscan/lvscan/lvs/vgs)
>
> PKG_NAME=LVM2
> PKG_VERSION=2.02.168
> PKG_URL=LVM2.2.02.168.tgz
> PKG_MD5=00209bdd6befe9a7330f162909313ae8
> PKG_DATE=2016-12-01
>
> This issue is also seen in LVM2-2.02.171.
Please check if this fix is applied to your version:
https://sourceware.org/git/?p=lvm2.git;a=commit;h=c459f23565e86eb9a8a116995cda7dcaed858b9f
AFAICT all the problems you sent are the fault of the memory debugging
code, not the original problem. You need to compile lvmetad with
debugging, but not memory debugging. Then gdb should give relevant
backtraces.
Dave
More information about the linux-lvm
mailing list