16 Oct
2016
16 Oct
'16
11:04 a.m.
On 10/16/2016 05:42 AM, George N. White III wrote:
I don't remember the date, specifically, and it's not clear what the circumstances are. One of the consequences of on-line fs checking is that errors tend to be detected long after they actually occur.Not sure what you mean -- certainly with most linux distros fsck gets run at intervals on clean reboot and does on rare occasions find problems to repair.
Yes, but as we've discussed, fsck.xfs (and hence, fsck -t xfs) is a no-op. XFS is checked and repaired on-line, as it's used, in the case of simple errors. If corruption is introduced, it may not be found until some time later, in which case xfs_repair will be needed.