Pmm-data volume not exists

1

Hi,

We upgraded PMM from version 2.44 to 3.4. After the upgrade, we are unable to see the pmm-data volume in docker status. However, the dashboards and backups are running fine.

FYI:

[root@duppmm101 2025-10-08]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1ce0336a67de percona/watchtower “/watchtower --clean…” 8 days ago Up 8 days (healthy) 8080/tcp watchtower
973f6ea40e66 percona/pmm-server:3 “/opt/entrypoint.sh” 8 days ago Up 4 hours (healthy) 8080/tcp, 0.0.0.0:443->8443/tcp pmm-server
[root@duppmm101 2025-10-08]#

Thanks,

Suman.A

2

Hi, can you share what mounts are associated with the new pmm-server container?

say, with: docker inspect pmm-server | grep -A 10 “Mounts”

3

Its giving empty output

[root@xxxx 2025-10-08]# docker inspect pmm-server | grep -A 10 “Mounts”
[root@duppmm101 2025-10-08]#

[root@xxxx 2025-10-08]# docker inspect pmm-server | grep -A 10 “Mounts”
[root@xxxx 2025-10-08]#
[root@xxxx 2025-10-08]#
[root@xxxx 2025-10-08]#
[root@xxxx 2025-10-08]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 3.8G 8.0K 3.8G 1% /dev/shm
tmpfs 1.5G 126M 1.4G 9% /run
/dev/mapper/rl-root 28G 6.7G 22G 24% /
/dev/sda1 960M 420M 541M 44% /boot
/dev/mapper/vg_pmmbackups-lv_pmmbackups 295G 61G 219G 22% /db/pmmbackups
/dev/mapper/vg_db-lv_data 590G 191G 370G 35% /db/data
overlay 590G 191G 370G 35% /db/data/pmmdata/overlay2/66230def2a9e3bc7d665c0763173d775ff60c422200b5ec09af0327835101767/merged
overlay 590G 191G 370G 35% /db/data/pmmdata/overlay2/cb1dde6b237e79e46006c6601b0666151e3538dc8979619d5c294689fc8ca4ac/merged
tmpfs 765M 0 765M 0% /run/user/13425
4

Hi Michael,

Can you please check and give the suggestion on above out put.

Thanks,

Suman.A

5

It’s possible that pmm3 is using the same docker overlay mounts that appear in your output. Can we see the mapping between the mounts and the running containers? Something like:

for container in $(docker ps --all --format '{{ .Names }}'); do
    echo "$(docker inspect $container --format '{{.GraphDriver.Data.MergedDir }}' | \
      grep -Po '^.+?(?=/merged)'  ) = $container"
done

Also, you can use the editor formatting to format command outputs.

6

Hi Michael,

Please find the below out put.

[root@xxxx de.suanumolu]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1ce0336a67de percona/watchtower “/watchtower --clean…” 9 days ago Up 9 days (healthy) 8080/tcp watchtower
973f6ea40e66 percona/pmm-server:3 “/opt/entrypoint.sh” 9 days ago Up 20 hours (healthy) 8080/tcp, 0.0.0.0:443->8443/tcp pmm-server
[root@xxxx de.suanumolu]#
[root@xxxx de.suanumolu]#
[root@xxxx de.suanumolu]#
[root@xxxx de.suanumolu]# for container in $(docker ps --all --format ‘{{ .Names }}’); do
echo “$(docker inspect $container --format ‘{{.GraphDriver.Data.MergedDir }}’ |
grep -Po ‘^.+?(?=/merged)’ ) = $container”
done
/db/data/pmmdata/overlay2/cb1dde6b237e79e46006c6601b0666151e3538dc8979619d5c294689fc8ca4ac = watchtower
/db/data/pmmdata/overlay2/66230def2a9e3bc7d665c0763173d775ff60c422200b5ec09af0327835101767 = pmm-server
[root@xxxx de.suanumolu]#
7

Yeah the overlay mounts are tied to your PMM 3 set-up, and that’s where its data currently is. How did the upgrade from PMM v2 to v3 happen though? Because it looks like PMM 3 wasn’t started with volumes.

8

Hi Michael,

We followed the below steps to upgrade the pmm from 2.44 to 3.4

curl -o get-pmm.sh https://www.percona.com/get/pmm
*chmod +x get-pmm.sh
./get-pmm.sh -n pmm-server -b
*
It went fine without any issues. However, after the upgrade, we noticed that the pmm-data volume is not showing, But backups and dash boards are looking good.

Thanks,

Suman.A