#Getting flexcache error while doing image validation

1 messages · Page 1 of 1 (latest)

vestal flame
#

ONTAP Image validation fails saying disable writeback on flexcache to upgrade the cluster but there is no writeback enabled on the cluster.

Any way to overcome this, all suggestions say to delete the flexcache and recreate which is not an ideal solution considering the fact that the flexcache setup is already done and into production.

chilly badge
#

From what version to what version are you upgrading?

vestal flame
#

9.14 to 9.15

chilly badge
#

can you do a volume flexcache config show -fields is-writeback-enabled?

jovial river
#

This should only be showing if the tech preview of FlexCache writeback in ONTAP 9.12.1 was enabled. Maybe a test volume somewhere?

chilly badge
#

ywah that's what I was suspecting 🙂

vestal flame
#

I could see that writeback-enabled parameter is false

vestal flame
#

flexcache config show -instance (volume flexcache config show) Vserver Name: svm Cache Volume Name: vol Is CIFS Access Enabled: true Is NFSv4 Access Enabled: true Is Writeback Enabled: false Is Relative Sizing Enabled: false Relative FlexCache Size Percentage: 10 Is atime based Scrubbing Enabled/Disabled: - Days after which an inactive file is scrubbed: - Is CIFS CHANGE_NOTIFY Enabled/Disabled: false Vserver Name: svm Cache Volume Name: vol_j Is CIFS Access Enabled: true Is NFSv4 Access Enabled: true Is Writeback Enabled: false Is Relative Sizing Enabled: false Relative FlexCache Size Percentage: 10 Is atime based Scrubbing Enabled/Disabled: false Days after which an inactive file is scrubbed: 30 Is CIFS CHANGE_NOTIFY Enabled/Disabled: false Vserver Name: svm Cache Volume Name: vol_k Is CIFS Access Enabled: true Is NFSv4 Access Enabled: true Is Writeback Enabled: false Is Relative Sizing Enabled: false Relative FlexCache Size Percentage: 10 Is atime based Scrubbing Enabled/Disabled: false Days after which an inactive file is scrubbed: 30 Is CIFS CHANGE_NOTIFY Enabled/Disabled: false

vast breach
#

You need to check that on the cluster which holds the cache-volume (if there is any).

chilly badge
#

I vaguely remember there being some caveat when transitioning from the preview FlexCache writeback to the new one ... but I thought just disabling writeback would be enough

vast breach
#

Try updating to 9.14.1P8 first, I remember some FlexCache bug but in combination with SMV-DR and identity-preserve.

vestal flame
#

I checked the cache cluster and writeback is disabled there too.

vestal flame
vast breach
#

Which version are you currently on?

#

And is it showing as a warning or as an error?

vestal flame
#

Current version 9.14.1P1
Target version 9.15.1P2

chilly badge
#

do you maybe have other clusters peered for FlexCache that you're not (actively) using anymore?

vast breach
vestal flame
#

Let me test that and get back to you