Standalone backup agent for Linux servers and workstations on-premises or in the public cloud
Post Reply
gothaggis
Influencer
Posts: 11
Liked: 1 time
Joined: Feb 27, 2019 6:58 pm
Full Name: Geoff
Contact:

Snapstore portion was not ordered by Copy-on-Write block size

Post by gothaggis » Aug 21, 2019 12:21 pm

I'm seeing this in the logs occasionally - what does it mean?

veeamsnap:snapstore | WRN | Snapstore portion was not ordered by Copy-on-Write block size

Using CentOS 7.5, running unsupported kernel 5.1, and using BTRFS.

P.Tide
Product Manager
Posts: 5228
Liked: 450 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Snapstore portion was not ordered by Copy-on-Write block size

Post by P.Tide » Aug 22, 2019 5:10 pm

Hi,

It might happen when a snapshot portion is not aligned with COW-block, which means that the portion capacity cannot be fully utilized. That might happen on ext3, for example. Do you have any other FS except BTRFS on that machine?

Thanks!

gothaggis
Influencer
Posts: 11
Liked: 1 time
Joined: Feb 27, 2019 6:58 pm
Full Name: Geoff
Contact:

Re: Snapstore portion was not ordered by Copy-on-Write block size

Post by gothaggis » Aug 23, 2019 12:48 pm

yes, have 2 xfs volumes - one is not backed up at all, and the other one is using file level restore instead of snapshots.

P.Tide
Product Manager
Posts: 5228
Liked: 450 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Snapstore portion was not ordered by Copy-on-Write block size

Post by P.Tide » Aug 23, 2019 4:10 pm

It can happen on XFS as well, though the probability of that is lower.

Thanks!

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests