Julien ÉLIE <jul...@trigofacile.com> writes: >> FWIW, tradindexed uses that inode number as an optimization. When >> expireover rewrites the data file, it does so in a way that changes the >> inode number (and updates that field in the index file), which >> communicates to any other process such as running nnrpd instances with >> open maps that the data file has changed and should be re-opened to >> pick up the new data file. Therefore, these error messages shouldn't >> result in any incorrect behavior (I think); it will just make things >> slower because the data file may be re-opened unnecessarily even when >> it hasn't changed.
> As these messages do not result in any incorrect behaviour, couldn't we > just lower their log level to notice instead of warn, and silent them in > innreport? We could, but it does indicate an actual problem, so I'd love to understand more about why this is happening. If ZFS does change the inodes on every reboot, another possible solution may be to ensure that expireover fixes the inode references (I'm not sure that it does right now in cases where it didn't need to change anything during expiration), which means the messages will only happen once after each reboot. I assume ZFS can't be changing them constantly without a reboot or a remounting of the file system, since presumably that would break lots of other software. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
