Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Arch configuration -- I/O stuck
Hi Pablo,
I've seen an 'ls' hang for more than a minute under 10.20 when there were a lot of
delayed writes pending on an
unrelated file-system. A colleague of mine (Chris Bunting) did some testing to
reproduce the problem and concluded that
all filesystems of the same type (JFS or HFS) were affected. HP made some kernel
changes for 11.0 that have reduced the
severity of the problem, but it can still occur.
If your case the archive writes are not delayed writes because Oracle explicitly opens
the files in synchronous mode, so
you should not see a delay any longer than that corresponding to the time that it
would take your Symmetrix box to
destage the cache allocations for the target LUNs, unless there happens to be
simultaneous heavy delayed write activity
elsewhere on the system.
The failure of the multiblock_read_test.sql script probably indicates that the "large"
table that you scanned already
had a large number of block in the cache.
@ Regards, @ Steve Adams @ http://www.ixora.com.au/ - For DBAs @ http://www.christianity.net.au/ - For all
-----Original Message-----
Sent: Friday, 2 November 2001 6:39
To: Steve Adams; Multiple recipients of list ORACLE-L
Steve, thanks for the help and for the url and the advice of stripping.
I don't understand what I'm pasting here , I'm executing a 'ls' in a FS that's in a different disk in differents LUNs (on the same Symmetrix), why is it still stucking. Shouldn't it be placed in a different queue??
"The 'ls' is probably getting stuck because the I/O is
very slow and file system metadata writes are stuck in
the I/O
queue while locks are held on the file system metadata
pending the completion of those writes."
One more question, besides what you just advised me, I've been trying to reduce ARCH bandwidth (as I read in a TIP at your site), to spread ARCH work along more time and reduce the impact in foreground processes. So I've set log_archive_buffers from 4 to 2 and today I've tried to set log_archive_buffer_size to the MAX_IO_SIZE of the OS. But I found a problem with this.
I tried to check what was the MAX_IO_SIZE, so I used 10046 event and check at scattered reads in a big FTS (as you do in your scripts) and I always got p3=5. I checked this into 2 differents databases running on the same box. Both reported p3=5 (5 blocks I think), but the surprise is that one of them has got db_block_size=4K and the other db_block_size=8K.
How can it be possible? according to this test MAX_IO_SIZE could be 20K or 40K. what's wrong here?
And something worst, MAX_IO_SIZE can't be so small, right? I thought it was 1MB or 512K in HP-UX 11.0
thannks for your time.
TIA
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Steve Adams INET: steve.adams_at_ixora.com.au Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Thu Nov 01 2001 - 21:03:38 CST
![]() |
![]() |