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.
-
- Influencer
- Posts: 19
- Liked: 2 times
- Joined: Feb 27, 2019 6:58 pm
- Full Name: Geoff
- Contact:
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Snapstore portion was not ordered by Copy-on-Write block size
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!
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!
-
- Influencer
- Posts: 19
- Liked: 2 times
- Joined: Feb 27, 2019 6:58 pm
- Full Name: Geoff
- Contact:
Re: Snapstore portion was not ordered by Copy-on-Write block size
yes, have 2 xfs volumes - one is not backed up at all, and the other one is using file level restore instead of snapshots.
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Snapstore portion was not ordered by Copy-on-Write block size
It can happen on XFS as well, though the probability of that is lower.
Thanks!
Thanks!
Who is online
Users browsing this forum: No registered users and 8 guests