Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

PMM 1.17.2 resize-xfs cronjob mail problem.

Description

Hello!

I set up PMM in a virtual machine and whilst all works nicely, there seems to be a cronjob running every 5 minutes that tries to resize /dev/sdb. As I understand it's meant to resize the disk automatically when you change its virtual size.

The problem however is that it's sending cron mails to the root user every 5 minutes, whilst not actually doing anything.

Cron <root@pmm> /var/lib/cloud/scripts/per-boot/resize-xfs
Physical volume "/dev/sdb" changed 1 physical volume(s) resized or updated / 0 physical volume(s) not resized Size of logical volume DataVG/ThinPool_tmeta unchanged from 100.00 MiB (25 extents). Logical volume DataVG/ThinPool_tmeta successfully resized. Size of logical volume DataVG/ThinPool_tdata unchanged from 399.80 GiB (102349 extents). Logical volume DataVG/ThinPool_tdata successfully resized. New size (81920 extents) matches existing size (81920 extents).

How to test

None

How to document

None

Attachments

1
  • 07 Nov 2019, 12:30 PM

Smart Checklist

Activity

Show:

Reio Remma April 27, 2020 at 10:20 PM

Painfully, after upgrading to 2.5.0 server/client, the problem persists.

 

Every 5 minutes I get a mail:

 

Physical volume "/dev/sdb" changed
1 physical volume(s) resized or updated / 0 physical volume(s) not resized
Reducing 1%VG to remaining free space 100.00 MiB in VG.
New size (25 extents) matches existing size (25 extents).
Reducing 100%VG to remaining free space 399.80 GiB in VG.
New size (102349 extents) matches existing size (102349 extents).
New size (81920 extents) matches existing size (81920 extents).
data size unchanged, skipping
meta-data=/dev/mapper/DataVG-DataLV isize=512 agcount=2560, agsize=32768 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=0 spinodes=0
data = bsize=4096 blocks=83886080, imaxpct=25
= sunit=64 swidth=64 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=64 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0

 

Forwarding root mail to my actual mail address is a bad idea. slightly smiling face

Lalit Choudhary November 7, 2019 at 12:31 PM
Edited

Hi

Thank you for the report.

Verified with PMM 1.17.2 Virtual Appliance (OVF) image on VirtualBox 

I can see the following message in every 5 mins,

cat /var/spool/mail/root

From root@localhost.localdomain Thu Nov 7 11:45:01 2019 Return-Path: <root@localhost.localdomain> X-Original-To: root Delivered-To: root@localhost.localdomain Received: by localhost.localdomain (Postfix, from userid 0) id 8C1CD400A5AF; Thu, 7 Nov 2019 11:45:01 +0000 (UTC) From: "(Cron Daemon)" <root@localhost.localdomain> To: root@localhost.localdomain Subject: Cron <root@localhost> /var/lib/cloud/scripts/per-boot/resize-xfs Content-Type: text/plain; charset=UTF-8 Auto-Submitted: auto-generated Precedence: bulk X-Cron-Env: <XDG_SESSION_ID=2> X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/0> X-Cron-Env: <LANG=en_US.UTF-8> X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=root> X-Cron-Env: <USER=root> Message-Id: <20191107114501.8C1CD400A5AF@localhost.localdomain> Date: Thu, 7 Nov 2019 11:45:01 +0000 (UTC)

 

Details

Assignee

Reporter

Priority

Components

Labels

Needs QA

Yes

Needs Doc

Yes

Affects versions

Environment

PMM Server 1.17.2 running in as a VMWare guest.

2 CPU cores, 2GB RAM.

Smart Checklist

Created November 4, 2019 at 6:11 PM
Updated March 27, 2024 at 2:59 PM

Flag notifications