Oleg Bolshakov
|
Re: Disk Errors are cached?
|
Oleg Bolshakov
09/19/2016 4:54 AM
post116811
|
Re: Disk Errors are cached?
Hi Andy,
> 1) I see that dcheck has a 'disable drive error correction' options. Is this a suitable candidate ?
It seems that this has sense for Fsys.ata only (old driver) to disable ECC check.
> 2) Is there an ioctl() that will do the cache invalidation?
Did you try sync utility to flush caches? Did it help?
> 3) Is all this caused by Fsys.Fsys.atapi caching I/O Errors when they shouldn't be cached.? If so can that behavior be
stopped?
Disk cache is driven by Fsys, not the disk driver. I can't know how to disable caching in this particular case.
> We have the source and the error happens in one place. If we could invalidate the cache , retry and move on (or not
if its a real error) . This would help production and allow us time to get the best replacement.
I understand this. Unfortunately, I can't debug the issue without the ability to reproduce it. And even more the
debugging may take quite a few time.
Respectfully,
Oleg
19 сент. 2016 г., в 9:44:55, Andy Rhind <community-noreply@qnx.com> написал:
> Oleg:
>
> Yes II agree the original problem is hard to reproduce and 5 days is forever, if testing. 5 days is a very short time
in production. I believe the problem is the Commell with the motherboard. Finding a QNX4 compatible replacement will
take time and cost, then it needs to be tested for the current problem. We have a possible replacement for the ARaid,
but testing is ongoing.
>
> Sure the original, temporary I/O Error happens and is a bad thing and needs to be stopped. I posted here to try to
understand the stickyness of the error, to understand its reason and find a way to get around it in the short term.
>
> We have the source and the error happens in one place. If we could invalidate the cache , retry and move on (or not
if its a real error) . This would help production and allow us time to get the best replacement.
>
> 1) I see that dcheck has a 'disable drive error correction' options. Is this a suitable candidate ?
>
> 2) Is there an ioctl() that will do the cache invalidation?
>
> 3) Is all this caused by Fsys.Fsys.atapi caching I/O Errors when they shouldn't be cached.? If so can that behavior be
stopped?
>
>
> Thanks,
> Andy
>
>
>
>
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post116810
> To cancel your subscription to this discussion, please e-mail qnx4-community-unsubscribe@community.qnx.com
|
|
|