Auto coalescing of disks

r1

@chrispage1 said in Auto coalescing of disks:

Apr 7 16:07:09 node-01 SMGC: [20480] text = session.xenapi.host.call_plugin(slave, "on-slave", "multi", args)

Seems the issue is here. Are all your slaves in pool healthy?

chrispage1

@r1 They are reporting to be at least, all green on the UI -

Any way I can check further?

Chris.

olivierlambert

By default the UI will only display running hosts. Be sure to have an empty search field.

chrispage1

@olivierlambert thanks - that's definitely all the hosts. Only three on this system. Any way to check each host at a deeper level?

Chris

olivierlambert

Input/output error isn't a good sign

Try to reboot all your hosts and see if the issue persist. Also check dmesg.

chrispage1

@olivierlambert ah - would the input/output error be on the nodes itself or the SR?

We have seen this input/output error before when attempting to snapshot or migrate VM's -

 "code": "SR_BACKEND_FAILURE_81",
  "params": [
    "",
    "Failed to clone VDI [opterr=['XENAPI_PLUGIN_FAILURE', 'multi', 'CommandException', 'Input/output error']]",
    ""
  ],

I can reboot the nodes but would be a little hesitant due to potential downtime, etc. Would restarting the tool stack help?

dmesg isn't reporting anything particularly concerning.

Appreciate your support on this,
Chris.

olivierlambert

It's on the SR here. The storage code is reporting the issue, so that's why coalesce isn't happening.

chrispage1

@olivierlambert thanks. The only other thing - I was using templates so I notice on my storage that one block consists of 6 base copies & 3 VDI's.

In this format, I have issues migrating and snapshotting them. However, if I power them off, snapshot, run a full clone, and use the new clone they work fine (migratable, snapshottable, bootable). Any ideas why this might be and could this be the cause of the coalesce issue?

Thanks,
Chris.

chrispage1

@olivierlambert Hi, I've been keeping an eye on dmesg and getting the following -

[Thu Apr 8 20:26:51 2021] device-mapper: ioctl: unable to remove open device VG_XenStorage--767a9d9c--55aa--0898--fe10--400ee856bdce-clone_ba7ea2dd--4684--4cc9--9ccd--ba1909cda656_1

I don't know if this could possibly be related to the exceptions I am seeing?

Thanks,
Chris.

olivierlambert

You have weird issues on your storage (I/O error on badly named VHD, hard to tell without investigating further)

chrispage1

@olivierlambert thanks - I'll continue to look into it.