Invalid logical volume offset

Backup agent for Linux servers and workstations on-premises or in the public cloud

Invalid logical volume offset

Veeam Logoby JWester » Fri Jun 02, 2017 9:30 am

Hi,

we just started to test the Linux client on some larger customers servers.
Unfortunately the 1st server already ran into an error.
It's an Ubuntu system.
Linux srv2 3.13.0-117-generic #164-Ubuntu SMP Fri Apr 7 11:05:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

GUI:

Code: Select all
      11:12:20        Starting incremental backup to [veeam-ep01vp]ZFS
      11:12:25        Backed up sda 9 MB at 4 MB/s                                                                      00:00:02
      11:12:32        [error] Backing up system                                                                         00:00:00
      11:12:35        [error] Failed to perform backup
      11:12:35        [error] Invalid logical volume offset: [1048576]. Requested offset: [10738466816]
      11:12:35        [error] Failed to open emulated disk
      11:12:35        [error] Failed to open disk for read
      11:12:35        [error] Failed to upload disk
      11:12:35        [error] Agent failed to process method {DataTransfer.SyncDisk}
      11:12:35        [error] Processing finished with errors at 2017-06-02 11:12:35 CEST


From Agent.Source.Log:

Code: Select all
[02.06.2017 11:12:32] <139743169853184> dt     |     Opening disk. Disk path: [emulated://<EmulatedDiskSpec><Layout><Lvm VgName="system"
 VgUUID="tdlX4G-YyCr-wWmR-H42K-aQpg-9xvg-jUiN82" PeSizeBytes="4194304"><LogicalVolumes><LogicalVolume LvName="var" LvUUID="vQIKsq-IKzd-8
nPy-cTUT-8N2I-lrcM-1YEjU5" Length="26843545600" Offset="10738466816"><UnderlyingDevice><VeeamSnap DevMajor="252" DevMinor="1" /></Underl
yingDevice></LogicalVolume><LogicalVolume LvName="root" LvUUID="EuFUYM-s3o5-BF6q-Upty-djPR-vQVB-G0DJIE" Length="10737418240" Offset="375
82012416"><UnderlyingDevice><VeeamSnap DevMajor="252" DevMinor="3" /></UnderlyingDevice></LogicalVolume><LogicalVolume LvName="usr" LvUU
ID="wwBz1Y-wqC5-KXaw-ueKl-9jF7-hB2n-axvuBp" Length="10737418240" Offset="1048576"><UnderlyingDevice><VeeamSnap DevMajor="252" DevMinor="
4" /></UnderlyingDevice></LogicalVolume></LogicalVolumes></Lvm></Layout></EmulatedDiskSpec>]. Is read-only: [true]. Failed.
[02.06.2017 11:12:32] <139743169853184> dt     |   Opening live disk source. Disk path: 'emulated://<EmulatedDiskSpec><Layout><Lvm VgNam
e="system" VgUUID="tdlX4G-YyCr-wWmR-H42K-aQpg-9xvg-jUiN82" PeSizeBytes="4194304"><LogicalVolumes><LogicalVolume LvName="var" LvUUID="vQI
Ksq-IKzd-8nPy-cTUT-8N2I-lrcM-1YEjU5" Length="26843545600" Offset="10738466816"><UnderlyingDevice><VeeamSnap DevMajor="252" DevMinor="1"
/></UnderlyingDevice></LogicalVolume><LogicalVolume LvName="root" LvUUID="EuFUYM-s3o5-BF6q-Upty-djPR-vQVB-G0DJIE" Length="10737418240" O
ffset="37582012416"><UnderlyingDevice><VeeamSnap DevMajor="252" DevMinor="3" /></UnderlyingDevice></LogicalVolume><LogicalVolume LvName=
"usr" LvUUID="wwBz1Y-wqC5-KXaw-ueKl-9jF7-hB2n-axvuBp" Length="10737418240" Offset="1048576"><UnderlyingDevice><VeeamSnap DevMajor="252"
DevMinor="4" /></UnderlyingDevice></LogicalVolume></LogicalVolumes></Lvm></Layout></EmulatedDiskSpec>'. Failed.
[02.06.2017 11:12:32] <139743169853184> dt     | Performing disk upload (EmulatedDiskSpec>). Failed.
[02.06.2017 11:12:32] <139743169853184> cli    | ERR |Failed to process method {DataTransfer.SyncDisk}
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |Invalid logical volume offset: [1048576]. Requested offset: [10738466816].
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |--tr:Failed to build emulated LVM physical volume.
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |Failed to open emulated disk.
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |Failed to open disk for read.
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |--tr:Failed to open live disk source.
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |Failed to upload disk.
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |--tr:Disk upload failed.
[02.06.2017 11:12:32] <139743169853184> cli    | >>  |An exception was thrown from thread [139743169853184].


Any ideas? Many thanks!

Joern
JWester
Service Provider
 
Posts: 53
Liked: 7 times
Joined: Mon Apr 04, 2011 8:56 am
Full Name: Joern Westermann

Re: Invalid logical volume offset

Veeam Logoby skochetkov » Fri Jun 02, 2017 2:00 pm 1 person likes this post

Hello Joern,

Please submit a support case via CP, attach the product logs and post here the case number.

Here you can find an article which describes how to collect the product logs: https://helpcenter.veeam.com/docs/agent ... tml?ver=10

Thanks
skochetkov
Veeam Software
 
Posts: 24
Liked: 3 times
Joined: Thu Feb 12, 2015 12:36 pm
Full Name: Sergey Kochetkov

Re: Invalid logical volume offset

Veeam Logoby JWester » Sun Jun 04, 2017 6:01 pm

[ID# 02177891]
JWester
Service Provider
 
Posts: 53
Liked: 7 times
Joined: Mon Apr 04, 2011 8:56 am
Full Name: Joern Westermann

Re: Invalid logical volume offset

Veeam Logoby JWester » Wed Jun 07, 2017 10:39 am

Now the error message changed:

14:41:14 [error] Backing up system 1.1 TB at 39.8 MB/s (18%) 07:47:40
22:29:07 [error] Failed to perform backup
22:29:07 [error] Snapshot overflow
22:29:07 [error] Snapshot overflow
22:29:07 [error] Processing finished with errors at 2017-06-06 22:29:07 CEST

Yes, it's a large disk > 5 TB.
JWester
Service Provider
 
Posts: 53
Liked: 7 times
Joined: Mon Apr 04, 2011 8:56 am
Full Name: Joern Westermann

Re: Invalid logical volume offset

Veeam Logoby vmniels » Wed Jun 07, 2017 10:42 am

You can ask details via the support case to increase the snapshot value.
VCP-DCV
Veeam Certified Engineer
http://foonet.be
vmniels
Veeam Software
 
Posts: 1447
Liked: 319 times
Joined: Mon Jul 15, 2013 11:09 am
Full Name: Niels Engelen


Return to Veeam Agent for Linux



Who is online

Users browsing this forum: vClintWyckoff and 3 guests