I just worked through the process of growing the inodes on a volume that was quite close to running out (volume modify -files), this reflects on the primary volume but not the DR copy on our DR cluster, which is a RO volume. Since I can't modify that volume, I tried doing an update operation in OnCommand and that was successful but the "total files for user visible data" field does not reflect the new max on the RO DR copy after the update.
When inodes are increased automatically on a SnapMirror destination?
SnapMirror Type-XDP destination volumes increase their inode count when the SnapMirror source volume used inode count is greater than the total inode count of the SnapMirror destination volume When this occurs, the next SnapMirror update will increase the destination volume max inode count to match that of the source max inode count
To be honest. I have no idea why they don't manage it within the ONTAP code (for example with the volume autosize function). worth asking the account manager/partner (if you have) about existing/new RFE.
But in most cases, "Fix It" would be done before you ran out of files (warnings kick in at 80%).
12/17/2020 17:20:35 ontap9-tme-8040-01 ERROR wafl.vol.runningOutOfInodes: The file system on Volume FG_SM_400G__0001@vserver:7e3cc08e-d9b3-11e6-85e2-00a0986b1210 is using 80 percent or more of the files that can be contained on the volume.
In my case, I'd need to go to the CLI or GUI to resolve this manually.