Yes I get we should only be doing this if we think we have a problem. And the answer is, right now, we're not entirely clear.
We have a couple of issues our users are reporting to us, and its not clear to us if they are related, an FS problem or ACLs getting in the way. We do have users who are trying to work on files getting IO error, and we have an AFM sync issue. The disks are all online, I poked the FS with tsdbfs and the files look OK - (small files, but content of the block matches). Maybe we have a problem with DMAPI and TSM/HSM (could that cause IO error reported to user when they access a file even if its not an offline file??) We have a PMR open with IBM on this already. But there's a wanting to be sure in our own minds that we don't have an underlying FS problem. I.e. I have confidence that I can tell my users, yes I know you are seeing weird stuff, but we have run checks and are not introducing data corruption. Simon On 11/10/2017, 11:58, "[email protected] on behalf of [email protected]" <[email protected] on behalf of [email protected]> wrote: >Mostly, however, filesystem checks are only done if fs issues are >indicated by errors in the logs. Do you have reason to assume your fs has >probs? _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
