I have a Raid6 array that has been functioning perfectly well for the past several years, but out of a desire to keep path names organized I expanded the array to include 2 additional devices. While the expansion itself went well and all data seemed accessible at first, after about a week I encountered an error while accessing a file stating that the filesystem needed to be checked. Running e3fsck showed several errors stating that various inodes "seem to contain garbage". While I had an extra backup and was able to restore the corrupted files, this corruption seems to recur once or twice a week on different locations and files each time.
While I do have backups, I'd like to at least identify the cause of this corruption and fix it so I don't need to take my systems offline to repair and restore files.
Running 18.04.6 LTS (GNU/Linux 4.15.0-210-generic x86_64), filesystem is ext4 and consists of 6 main and 2 backup 8 terabyte drives in a raid 6 format. The array prior to expansion had 4 main drives.
Drives are 4x HUH728080ALE601 and 4x HGST HUS728T8TAL
Initial error before running recovery tools is cannot access '*****': Structure needs cleaning