Re: SLES 9 SP4 and OCFS2

"Arun Singh" <[email protected]>
Newsgroups gmane.linux.suse.oracle.general
Message-ID <[email protected]>
Hi Werner,

This is not a normal behavior ;-)

Please have a look at http://oss.oracle.com/projects/ocfs2/dist/documentation/ocfs2_users_guide.pdf and post your question to Oracle ocfs2-users list(http://oss.oracle.com/pipermail/ocfs2-users/2008-January/002318.html  ). OCFS2 experts available on ocfs2-users list to take your questions.

PS: In case you all are wondering, which cool article is referred here: http://www.novell.com/coolsolutions/feature/18287.html

Regards,
Arun


>>> On 1/14/2008 at 8:55 AM, Werner Flamme <[email protected]> wrote:
> Hi everyone,
> 
> I read Arun's cool guide "Creating shared storage on SLES 10 using Xen
> and OCFS2". This was a good inspiration for me ;-)
> 
> I have 3 machines running SLES 9 SP 4. Two of them are connected to a FC
> RAID (Sun 3510), the 3rd will be connected soon. Since the machines are
> running SAP, I want to use OCFS2 for the common directory /usr/sap/trans.
> 
> I used Arun's guide and proceeded like he wrote from point 6 on (I don't
> have Xen). Everything went well, the config was propagated, 2 machines
> can mount the same filesystem in rw mode without scrambling it.
> 
> But: when I create a file, eg. /usr/sap/trans/mytest, this file is not
> shown on the other machine. Both nodes show active heartbeat. Is this
> expected behaviour? (not for me, though ;-))
> 
> After unmount und remountig the fs again, the file is shown.
> 
> Upgrading to SLES 10 SP 1 is not an option yet. What else do I have to
> do, that a file created on one node is accessible on another without
> having to unmount and mount again? BTW, mount -o remount does not work.
> 
> Regards,
> Werner





-- 
To unsubscribe, email: [email protected]
For additional commands, email: [email protected]
Please see http://www.suse.com/oracle/ before posting
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.