LOL., JL. Probably an elevator algorithm on failures. It was probably
telling someone they'd better copy the contents somewhere real soon now and
retire the device.
Last time I saw wasn't RHEL but actual UNIX and the root cause was no flap
on the read_only button that was far too easy to bump.
I don't even know if newer disk farms have a read_only button.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Jonathan Lewis
Sent: Wednesday, April 18, 2018 3:51 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: IO Freeze ON RHEL 6.6 and hence high log file sync
The last time this happened to me it was because the disk system had decided
to do a diagnostic self-check every 15 minutes - I can't remember why,
though.
Regards
Jonathan Lewis
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on
behalf of Purav Chovatia <puravc@xxxxxxxxx>
Sent: 18 April 2018 18:25
To: oracle-l@xxxxxxxxxxxxx
Subject: IO Freeze ON RHEL 6.6 and hence high log file sync
We are on RHEL 6.6 running a 2-node Oracle 12c RAC.
All of a sudden, for 2-3 minutes, DATADG (asm diskgroup containing all data
files) freezes for 2-3minutes with iostat showing 100% utilisation, very
high svctm and very high write_await. But the r/s, w/s rsec/s and wsec/s is
0. Meaning no IO but still disk fully busy. So it's like a freeze.
Has anybody experienced this and can somebody help as to what could be the
reason?
Transparent huge pages were not disabled and general huge pages were not
configured. Now both done.
Many thanks
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
