Skip to main content
Question

Issue with Block Mode Snapshot Export Failing using OpenEBS Mayastor


Hello Veeam Community,

I'm encountering an issue with the volume mode set to raw block mode. The snapshot export process fails, and the error logs indicate a command terminated with exit code 1. The relevant part of the error message is:

command terminated with exit code 1.

k10kopia: error: {"message":"size is not an integral multiple of block size","function":"kasten.io/bmd/go/volume/blockfile.(*brProducer).openForReading","linenumber":132,"file":"kasten.io/bmd/go/volume/blockfile/reader.go:132","fields":[{"name":"blockSize","value":"1.0 MiB"},{"name":"size","value":"1019 MiB"}],"cause":{"message":"invalid size"}}, try --help

Error: exit status 1

 

The key error seems to be: "size is not an integral multiple of block size"

The error encountered seems to be related to the backup process failing due to an issue with the block size not being an integral multiple of the volume size. Specifically, the error message indicates that the block size is 1.0 MiB, but the volume size is 1019 MiB, which is not divisible by 1 MiB.

Please find attached the full log from the Kasten side. Note that it works fine with the volume mode set to filesystem mode.

Has anyone encountered a similar issue or have any suggestions on how to resolve this? Any help would be greatly appreciated!

 

Forum|alt.badge.img+1
  • Comes here often
  • June 11, 2024

Hello @lpavanvenkat ,

 

Is this happening with all volumes you attempt to backup? or is this occurring with one in particular policy run. 

 

Thanks

Emmanuel


@EBrockman , it happens for every attempt for block mode volumes with k10 policy where Backups via Snapshot Exports is enabled.

EBrockman wrote:

Hello @lpavanvenkat ,

 

Is this happening with all volumes you attempt to backup? or is this occurring with one in particular policy run. 

 

Thanks

Emmanuel

 


Forum|alt.badge.img+1
  • Comes here often
  • June 11, 2024

Hello @lpavanvenkat,

 

Could you send yaml of one of the PVC and PV in question.

 

Thanks

Emmanuel


EBrockman wrote:

Hello @lpavanvenkat,

 

Could you send yaml of one of the PVC and PV in question.

 

Thanks

Emmanuel

Hi @EBrockman , PFA yaml txt files pvc.txt and pv.txt .


Forum|alt.badge.img+1
  • Comes here often
  • June 13, 2024

Hello @lpavanvenkat 

 

Would it be possible to create a test PVC with 1024MiB as the capacity, and attempt to back just that volume up.

 

Thanks

Emmanuel


EBrockman wrote:

Hello @lpavanvenkat 

 

Would it be possible to create a test PVC with 1024MiB as the capacity, and attempt to back just that volume up.

 

Thanks

Emmanuel

Hi @EBrockman ,
Tried the method you suggested, but still facing the same issue.


k10kopia: error: {"message":"size is not an integral multiple of block size","function":"kasten.io/bmd/go/volume/blockfile.(*brProducer).openForReading","linenumber":132,"file":"kasten.io/bmd/go/volume/blockfile/reader.go:132","fields":[{"name":"blockSize","value":"1.0 MiB"},{"name":"size","value":"1019 MiB"}],"cause":{"message":"invalid size"}}, try --help

Thanks
Pavan


We are still facing this issue, can we have any updates on this ? Also, does block volume snapshot backup supported in free version ? 


Hi ,

After adding annotation(k10.kasten.io/sc-supports-block-mode-exports: "true") to the storage class a new error was observed.

The Storage class support block mode volumes and still the error was observed
Storage class also passes the block mode volume test using primer tool.

Error:
 

 Failed to copy artifacts

 Error converting snapshots

 failed to create backup object

 failed to get or create block mode uploader

 volume's storage class does not support block mode export

 volume's storage class does not support block mode export

 

Storage Class Defination:


allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  annotations:
    k10.kasten.io/block-mode-uses-storage-api: disable
    k10.kasten.io/sc-supports-block-mode-exports: "true"
  creationTimestamp: "2025-04-08T09:45:42Z"
  name: mayastor-1
  resourceVersion: "719027"
  uid: 00849126-e4ef-4cea-b02c-637e67684aa5
parameters:
  protocol: nvmf
  repl: "1"
  thin: "true"
provisioner: io.openebs.csi-mayastor
reclaimPolicy: Delete
volumeBindingMode: Immediate

 

Tried annotating SC  to disable transfer using storage-api and it still failed, failing only at the export stage.
​@EBrockman Can you please advise?


Comment