[Ocfs2-users] Anomaly when writing to OCFS2

[John Gardner]

Hi everyone

We have a problem when writing a some files to OCFS2 and I hope perhaps some of you may be able to help.  I'll outline our system first.

We have a Oracle RAC system about to go into service.  There are two DB nodes running Oracle Enterprise Linux 5u4 (64bit) with kernel 2.6.18-164.15.1.0.1.el5.  ASM is handling all of the discs apart from Parallel Concurrent Processing (PCP) which we have installed on an OCFS2 shared disc between the two nodes.  The RAC system is all working correctly, but we are experiences anomalies when certain files are written to the OCFS2 PCP disc.  Our OCFS2 install information is;

ocfs2-tools-1.4.4-1.el5.x86_64
ocfs2console-1.4.4-1.el5.x86_64
ocfs2-2.6.18-164.15.1.0.1.el5-1.4.7-1.el5.x86_64

Device: /dev/emcpoweri1
Mountpoint: /u03
Version: 0.90
Cluster Size: 8K
Block Size: 4K

OK, Now for the problem.  When an Oracle Interface/Data Load Program is started  (this loads data into the db) through Concurrent Manager, we see the log file for this operation (which stores errors etc.) being create in the out directory under $APPLCSF/$APPLOUT, but it is always of 0Kb.  We know this worked on one of our tests systems (using NFS rather than OCFS2) so we know that the process works, we just don't know why it doesn't work under OCFS2.

 In order to try and narrow the problem down, we started to examine the tmp directory at $APPLPTMP (also on the OCFS2 disc) and we could see the file being written to the tmp directory successfully,  but at the point where the file is copied over to the to the out directory it somehow sets the file to 0Kb and the contents of the log file is lost.  As an experiment, we moved the tmp directory to an ext3 partition and pointed $APPLPTMP to this new location via a sym link... since doing this everything now works, and the fully populated output log file is written to $APPLCSF/$APPLOUT (still on the OCFS2 partition) correctly.  Unfortunately, we can't leave the tmp directory on the ext3 partition as it needs to be shared, so my question is quite simple really, does anyone know why the action of writing the log file to this temp directory should cause such an anomaly?

I'd greatly appreciate any input that can be given.

Thanks and Regards

John





This email and any files transmitted with it are intended solely for the named recipient and may contain sensitive, confidential or protectively marked material up to the central government classification of ?RESTRICTED" which must be handled accordingly.  If you have received this e-mail in error, please immediately notify the sender by e-mail and delete from your system, unless you are the named recipient (or authorised to receive it for the recipient) you are not permitted to copy, use, store, publish, disseminate or disclose it to anyone else.


E-mail transmission cannot be guaranteed to be secure or error-free as it could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses and therefore the Council accept no liability for any such errors or omissions.  


Unless explicitly stated otherwise views or opinions expressed in this email are solely those of the author and do not necessarily represent those of the Council and are not intended to be legally binding.

 

All Council network traffic and GCSX traffic may be subject to recording and/or monitoring in accordance with relevant legislation.



South Tyneside Council, Town Hall & Civic Offices, Westoe Road, South Shields, Tyne & Wear, NE33 2RL, Tel: 0191 427 1717, Website: www.southtyneside.info

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110401/4370216e/attachment.html