This explains why the forcedirectio mount option is required with NFS on solaris. But I always thought that setting the filesystemio_options parameter to directIO or setall caused the processes to open the files with the O_DIRECT flag. If so, would this then not cause the file to be accessed with directio despite any setting on the filesystem? I'm working mainly on linux these days (either with nfs or asm), so not much chance in testing this. Regards, Freek D'Hooge Uptime Oracle Database Administrator email: freek.dhooge@xxxxxxxxx tel +32(0)3 451 23 82 http://www.uptime.be disclaimer: www.uptime.be/disclaimer --- From: Gaja Krishna Vaidyanatha [mailto:gajav@xxxxxxxxx] Sent: vrijdag 11 februari 2011 22:47 To: D'Hooge Freek Cc: Oracle-L List Subject: Re: How much RAM is to much Hi Freek, What you said is true for filesystems that do NOT allow "direct I/O" mount options in their respective mount commands. But for those filesystems that do (i.e. vxfs, jfs etc) support the relevant direct I/O mount options, the direct I/O mount option has always (in my experience) been required in addition to setting filesystemio_options to SETALL. Setting just the filesystemio_options in the init.ora (in those cases) did not create the desired result. If you have observed the "lack of the mount option" in recent times on those filesystems where direct I/O mount options ARE supported (i.e. vxfs, jfs etc), please advise. There is always something to learn new each day :) Cheers, Gaja Gaja Krishna Vaidyanatha, Founder/Principal, DBPerfMan LLC http://www.dbperfman.com Phone - 001-(650)-743-6060 Co-author:Oracle Insights:Tales of the Oak Table - http://www.apress.com/book/bookDisplay.html?bID=314 Co-author:Oracle Performance Tuning 101 - http://www.amazon.com/gp/reader/0072131454/ref=sib_dp_pt/102-6130796-4625766 -- //www.freelists.org/webpage/oracle-l