Could not find LVM volume for

i create backup of ubuntu server 16 TLS with LVM.
i have this error Could not find LVM volume for …
ERROR LOG:
Errori
11/12/17 17:06
Creating snapshot of “/proc/8788/mounts” failed
Errori
11/12/17 17:06
Could not find LVM volume for mountpoint /proc
Errori
11/12/17 17:06
Creating snapshot of “/run/resolvconf/resolv.conf” failed
Errori
11/12/17 17:06
Could not find LVM volume for mountpoint /run
Errori
11/12/17 17:06
Creating snapshot of “/run/lock” failed
Errori
11/12/17 17:06
Could not find LVM volume for mountpoint /run/lock
Errori
11/12/17 17:06
Creating snapshot of “/run” failed
Errori
11/12/17 17:06
Could not find LVM volume for mountpoint /run
Errori
11/12/17 17:06
Creating snapshot of “/dev/shm” failed
Errori
11/12/17 17:06
Could not find LVM volume for mountpoint /dev/shm
Errori
11/12/17 17:06
Creating snapshot of “/dev/snd/seq” failed
Errori
11/12/17 17:06
Could not find LVM volume for mountpoint /dev
Errori
11/12/17 17:06
Creating snapshot of “/dev/snd/timer” failed
Errori
11/12/17 17:06
Could not find LVM volume for mountpoint /dev
Avvisi
11/12/17 17:14
Error getting complete file “fU5dsgK2lArvZIko522A|.symlink_run/systemd/sessions/2000” from webserver. Errorcode: CANNOT_OPEN_FILE (3)
Avvisi
11/12/17 17:14
Error getting complete file “fU5dsgK2lArvZIko522A|.symlink_run/systemd/system/session-2000.scope.d/50-After-systemd-logind\x2eservice.conf” from webserver. Errorcode: CANNOT_OPEN_FILE (3)
Avvisi
11/12/17 17:14
Error getting complete file “fU5dsgK2lArvZIko522A|.symlink_run/systemd/system/session-2000.scope.d/50-After-systemd-user-sessions\x2eservice.conf” from webserver. Errorcode: CANNOT_OPEN_FILE (3)
Avvisi
11/12/17 17:14
Error getting complete file “fU5dsgK2lArvZIko522A|.symlink_run/systemd/system/session-2000.scope.d/50-Description.conf” from webserver. Errorcode: CANNOT_OPEN_FILE (3)
Avvisi
11/12/17 17:14
Error getting complete file “fU5dsgK2lArvZIko522A|.symlink_run/systemd/system/session-2000.scope.d/50-SendSIGHUP.conf” from webserver. Errorcode: CANNOT_OPEN_FILE (3)
Avvisi
11/12/17 17:14
Error getting complete file “fU5dsgK2lArvZIko522A|.symlink_run/systemd/system/session-2000.scope.d/50-Slice.conf” from webserver. Errorcode: CANNOT_OPEN_FILE (3)
Avvisi
11/12/17 17:14
Error getting complete file “fU5dsgK2lArvZIko522A|.symlink_run/systemd/system/session-2000.scope.d/50-TasksMax.conf” from webserver. Errorcode: CANNOT_OPEN_FILE (3)
Avvisi
11/12/17 17:16
Not all folder metadata could be applied. Metadata was inconsistent.

lvm pvscan
/dev/webserver-vg/urbackup_snap_ab85b245a2c5c53a031c8fff91bd449f166bd77f2124dbe1: read failed after 0 of 4096 at 0: Errore di input/output
/dev/webserver-vg/urbackup_snap_ab85b245a2c5c53a031c8fff91bd449f166bd77f2124dbe1: read failed after 0 of 4096 at 209903878144: Errore di input/output
/dev/webserver-vg/urbackup_snap_ab85b245a2c5c53a031c8fff91bd449f166bd77f2124dbe1: read failed after 0 of 4096 at 209903935488: Errore di input/output
/dev/webserver-vg/urbackup_snap_ab85b245a2c5c53a031c8fff91bd449f166bd77f2124dbe1: read failed after 0 of 4096 at 4096: Errore di input/output
PV /dev/sda5 VG webserver-vg lvm2 [199,52 GiB / 20,00 MiB free]
Total: 1 [199,52 GiB] / in use: 1 [199,52 GiB] / in no VG: 0 [0 ]

Hi everyone,

Sorry I don’t have the solution, in fact I have the same issue… hope you won’t mind if I jump in your post because even if we don’t use the same snapshot mechanism (I use brtfs), we get the same kind of results…

16/12/17 16:04
Creating snapshot of “/run/resolvconf/resolv.conf” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type tmpfs
Erreurs
16/12/17 16:04
Creating snapshot of “/run/lock” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type tmpfs
Erreurs
16/12/17 16:04
Creating snapshot of “/run” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type tmpfs
Erreurs
16/12/17 16:04
Creating snapshot of “/dev/null” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type devtmpfs
Erreurs
16/12/17 16:04
Creating snapshot of “/dev/shm” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type tmpfs
Erreurs
16/12/17 16:04
Creating snapshot of “/dev/snd/seq” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type devtmpfs
Erreurs
16/12/17 16:04
Creating snapshot of “/dev/snd/timer” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type devtmpfs
Erreurs
16/12/17 16:04
Creating snapshot of “/proc/971/mounts” failed
Erreurs
16/12/17 16:04
Cannot create snapshot of file system with type

I suppose it has something to do with the snapshots script but I’m not too much comfortable with btrfs and I don’t understand well what it does…
I have this issue with 2.1.20 server (but it occurring since several versions) and Debian as well ubuntu client 2.1.16, 2.1.17 (and since several versions too)
in the same time, since you seem to have the same issue it is maybe more related the way the client expect snapshots of not “snapshotable” folders… I’m not sure if I’m clear…

Anyway, I’m very surprised because this is the first post I see with issue somewhat similar to mine and my installation is very standard, from fresh install of ubuntu or Debian and juste use the server’s provided command line to install the client then select btrfs (I suppose you choose lvm)
I’m surprised there is no more people touched by this or maybe I didn’t search enough in the forum…

Thank to any help, hints or enlightenment…
Best Regards,

Do try if it works better with the 2.2.x client (no need to upgrade the server). Otherwise it probably follows symlinks, so disabling symlink following for the backup path should do the trick too.

Hi Uroni !

Thank you for your answer :grin:
I would prefer to try 2.2.x client because, there is some VMs I backup where my customers have root access and I can’t tell “not to use symlinks or they won’t be backed up…”
Please where can I find 2.2.x client ? I only find 2.1.17…

Thanks again

https://forums.urbackup.org/t/server-2-2-5-beta-client-2-2-3-beta/

Hi !

Thank you very much for the help :slight_smile:
No more error with the new client ! For my concern the case is closed :smile:

Best Regards,