Dheerendar,
When the installer asks, you have to specify either a complete path with
file name on a OCFS2 filesystem mounted on both nodes or a raw device mapped to
the same location on both nodes.
In case you are using a raw device and it does not have the same location
on both nodes, you could use a symbolic link placed on the same location on
both nodes, and pointing to the raw device.
The installer will check if it can see the location from both nodes and
gives this error if it cannot.
If you are really using 10.1.0.2 this is a combination I never seen before
(RH 4.0 with 10.1). 10.1 is a bit dated now, perhaps you could try 10.2.
Regards,
Luis
"Eckenfels. Bernd" <[EMAIL PROTECTED]> wrote:
 Hello Dheerendar,
just a quick note: "The EMC device have been linked to raw devices " this is
IMHO not needed for Oracle anymore. (if you speak about /dev/rawX). You can use
the normal block devices and Oracle will open them with O_DIRECT flag.
What filesystem did you specify for CRS? I would suggest to use your own
small partitions.
Gruss
Bernd
---------------------------------
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dheerendar
Srivastav
Sent: Sunday, May 13, 2007 6:30 AM
To: [EMAIL PROTECTED]; [email protected]
Subject: Re: [Ocfs2-users] PBL with RMAN and ocfs2
Dear sir ,
We have used RHEL 4.0 with kernel 2.6.9-42.0.2.ELsmp with ocfs2 , we have
oracle 10g 10.1.0.2
I am working on a RAC installation (10.1.0.2)on RHEL 4.0 with EMC caliriion
shared storage . The EMC device have been linked to raw devices .
We are able to configure ocfs2 and
ASM . When we will installed CRS the error message show " oracle cluster
Registery can exists only as a shared file system file or as a shared raw
partion .
I would like request how to install the OCRFile .
Regards
Dheerendar Srivastav
Associate vice President -IT
Bajaj Capital Ltd.
New Delhi
----- Original Message -----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [email protected] <[email protected]>
Sent: Sat May 12 00:59:19 2007
Subject: RE: [Ocfs2-users] PBL with RMAN and ocfs2
Gaetano,
I am using RMAN with the default configuration here in RH 4.0, but I had
to change the I/O scheduler to the "deadline" I/O scheduler to prevent these
reboots, and increased the o2cb timeouts too. We had some just after
implementing but it seems very stable now. We increased the timeout here to
130, to account for SAN switch failures, powerpath and such.
I am still on 1.2.1 on the production nodes and it panics the machine,
which do is annoying even when the servers are on the same building, but there
are always messages on /var/log/messages of the killed node showing what
happened. Funny that 1.2.5 no longer shows these.
Regards,
Luis
Gaetano Giunta <[EMAIL PROTECTED]> wrote:
Well, I'm not 100% sure I solved the problem in a definitve way, but
here's the complete story:
1 - install, if you can, the latest release of ocfs2 + tools. The fact
that a node reboots instead of panicking (and resting in peace until manual
intervention) is a real life saver if you do not have immediate access to the
server farm. Plus timeouts are configurable.
2 - when a cluster node is rebooted by the ocfs daemon, a telltale
message is present on the console of the node. Messages from the ocfs daemon
will also be present in /var/log/messages on the other nodes, but looking at
those it is hard to understand if the dying node was shutdown by ocfs or by
other causes.
You can either sit in front of the screen or start the netdump service
on the rebooting node and the netdump-server service on a spare machine
(another node on the cluster is fine. For best results use a different nic
interconnect from the one used by ocfs.) If you are using red-hat the man pages
for both services are quite straightforward
3 - in our case, the log we netdumped said:
(6,0):o2hb_write_timeout:269 ERROR: Heartbeat write timeout to
device emcpowere2 after 12000 milliseconds
Heartbeat thread (6) printing last 24 blocking operations (cur = 7):
Heartbeat thread stuck at waiting for read completion, stuffing current
time into that blocker (index 7)
Index 8: took 0 ms to do submit_bio for read
[ ... ]
Index 7:
took 9998 ms to do waiting for read completion
*** ocfs2 is very sorry to be fencing this system by restarting ***
4 - thus we determined ocfs2 was indeed at fault. Operations on other
files where ok, but using rman to create a single 1,3 GB file on the ocfs disk
was somehow triggering an heartbeat timeout.
5 - we modified the configuration of our rman scripts to try to keep
the size of the files created smaller. We tested again, and there was no
reboot. I am not sure you can achieve the same result for failovers though -
the general idea is to keep io in smaller chunks (or slow it down somehow?)
6- As Sunil recommended (sorry, I think this was off list), we also
raised the ocfs timeout value for O2CB_HEARTBEAT_THRESHOLD. Precise
instructions for that can be found here:
http://oss.oracle.com/projects/ocfs2/dist/documentation/ocfs2_faq.html#TIMEOUT.
We decided to go with a value of 31. We did not raise timeouts for the network
keepalives (yet), since we are not using bonded nics for the ocfs2
interconnect. We might do that in the future if we find out that traffic on
that network is extremely high / the network unstable, though...
Hope it helps
Gaetano
-----Original Message-----
From: Mattias Segerdahl [mailto:[EMAIL PROTECTED]
Sent: Friday, May 11, 2007 10:00 AM
To: Gaetano Giunta
Subject: RE: [Ocfs2-users] PBL with RMAN and ocfs2
Hi,
Weâre having the exact same problem, if we do a failover
between two filers/sanâs, the server reboots.
So far I havenât found a solution to the problem, would you
mind trying to explain how you solved the problem, step by step?
Best Regards,
Mattias Segerdahl
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Gaetano Giunta
Sent: den 11 maj 2007 09:47
To: [email protected]
Subject: RE: [Ocfs2-users] PBL with RMAN and ocfs2
Thanks, but I had alreday checked out all logs I could find
(oracle and crs alerts, /var/log stuff) and there was no clear indication in
there.
The trick is the ocfs was sending the alert message to the
console only (I wonder why it does not also leva traces into syslog, my best
guess is it tries to shutdown as fast as it can, and sending a message to
console is faster than sending it to syslog - but I'm in no way a linux
guru...).
By using the netdump tool suggested by Sunil I managed to see
the console messages of the dying node (without having to phisycally be in the
server farm, which is 40 km away from my ususal workplace), and diagnosed the
ocfs2 heartbeat as "the killer".
Bye
Gaetano
-----Original Message-----
From: Luis Freitas [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 11:17 PM
To: Gaetano Giunta
Cc: [email protected]
Subject: Re: [Ocfs2-users] PBL with RMAN and ocfs2
Gaetano,
If o2cb or CRS is killing the machine, it usually
shows on /var/log/messages with lines explaining what happened. Take a look on
the /var/log/messages just before the last "syslogd x.x.x: restart".
Regards,
Luis
Gaetano Giunta wrote:
> Hello.
>
> On a 2 node RAC 10.2.0.3 setup, on RH ES 4.4 x86_64,
with ocfs 1.2.5-1, we are experiencing some troubles with RMAN: when the
archive log destination is on an ASM partition, and the backup detsination is
on ocfs2, running
>
> backup archivelog all format
'/home/SANstorage/oracle/backup/rman/dump_log/FULL_20070509_154916/arc_%d_%u'
delete input;
>
> consistently causes a reboot.
>
> The rman catalog is clean, and has been crosschecked
in every way.
>
> We tried on both nodes, and the node executing the
backup always reboots.
> I am thus inclined to think that it is not the ocfs2
dlm that triggers the reboot, because in that case the victim would always be
the second node.
>
> I also tested the same command using as backup
destination /tmp, and all was fine. The backup file of the archived logs is
1249843712 in size.
>
> Our local oracle guy went through metalink and said
there is no open bug/patch for that at this time.
>
> Any suggestions ???
>
> Thanks
> Gaetano Giunta
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> Ocfs2-users mailing list
> [email protected]
> http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
________________________________
Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
<http://us.rd.yahoo.com/evt=48245/*http:/autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM->
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
________________________________
Pinpoint customers
<http://us.rd.yahoo.com/evt=48250/*http://searchmarketing.yahoo.com/arp/sponsoredsearch_v9.php?o=US2226&cmp=Yahoo&ctv=AprNI&s=Y&s2=EM&b=50>
who are looking for what you sell.
pFQB×5DIb <--1DA <4zÖ˲+jjWjnzwj×wfÝ¡'ÞªzÈ
nǦj)b+ uÞ²Çjwfk'(Ö¢WjYrWyÖ§u'~'^Ø)ߢ*'!azu~bg ^{^× 'Þh稭 Þ²'&y+ub
azg azzܨqvZv+,zhjب))ࢷbnbz rxjب+)bn+^tz{rZqya(kƭ뢺ey iv&z\Ø(~^jw]zWzb&qbwl2צf&qbvzz-.uÆ©i^zbw(*'jw]zV
wi')+aaéVqm^+$j)\i'*'ݶ'zw .jz× j{aymifz{lÊà®vy˫ܦy.+-jw W(Ö1Ù¢+-bpÞ¥]yׯwMvÚÞiÙ¢j7+Z&Yajy2*.(Ú¶*'Ú&Ö¥.)
---------------------------------
SEEBURGER AG
Headquarters:
Edisonstraße 1
D-75015 Bretten
Tel.: 0 72 52/96-0
Fax: 0 72 52/96-2222
Internet: http://www.seeburger.de
e-mail: [EMAIL PROTECTED]
Vorstand:
Bernd Seeburger, Axel Haas, Michael Kleeberg
Vorsitzender des Aufsichtsrats:
Dr. Franz Scherer
Handelsregister:
HRB 240708 Mannheim
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
---------------------------------
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos._______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
