Hi, I sent an email to Mark Fisheh of Oracle Corp. & posted this issue at OTN under Linux thread this morning. I hope that someone among you might have experienced this and can help. On that basis, I am sending this to you too. I am stuck & will really appreciate if you can shed some light on this. Thanks. Anjan *********************************************************************************************************** I have a 2 node CentOS 4.5 86_64 system (kernel 2.6.9-55.EL). On this I installed Oracle OCFS2 1.2.7-1 (with exact kernel matching). After this I installed Oracle CRS 10.2.0.1 and that installation went fine. Then I tried to install Oracle RDBMS 10.2.0.1 and all the problems started from there. The /var/log/messages file got filled up with messages (giving some to avoid confusion): ocfs2_read_locked_inode: .. : ERROR: Invalid dinode #0 signature ocfs2_lookup: .. : ERROR: Unable to create inode .... Then OUI gave several error messages, e.g. .... Invalid stored block length on file ...../em/em.war followed by I/O error in file Errors in invoking to files ins_rdbms.mk and ins_ldap.mk Then /var/log/messages gave: OCFS2: ERROR (device ....): ocfs2_extend_file: Dinode # ...... has bad signature O' # I .... And the installation failed & CRS died. And the machines reboot. I ran fsck.ocfs2 -n /dev/...., it came clean. I have tested this several timnes & always same thing happening. If I use RAW partitions, everything works fine. So, the problem may be in the OCFS2 & OS/Oracle -- but, not sure how to bypass this. I have to have OCFS2 -- can't use RAW for various reasons. Can somebody please help me to resolve this? Thanks. *********************************************************************************************************** --------------------------------- Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. -------------- next part -------------- An HTML attachment was scrubbed... URL: oss.oracle.com/pipermail/ocfs2-users/attachments/20071126/f3e532aa/attachment.html
Anjan,
You dont need to share the database binaries, only the CRS and the datafiles.
You can do it to save disk space, but it is not mandatory. The CRS and datafiles
are much less stressfull to the filesystem structures as there is a reduced
number of large files, although they usually have a heavy i/o load, and stress
the disk subsystem and the locking algorithms.
So you can have two separated ext3 filesystems located at the same place on
each server, and one or more ocfs2 shared filesystems for the CRS and the
database datafiles. The Oracle installer takes care of copying the binaries
between the servers during the installation.
It might be usefull to try a lower version like 1.2.6, as you are using the
latest version available. I am using 1.2.4-2 here with RH 4.0 and kernel
2.6.9-42 and it seems rather stable, only needed to increase the timeouts. (But
I dont have the oracle_home shared.)
Also you might have a hardware problem somewhere on the SAN. And I still
have to check those mount options you sent...
One detail. I dont know if the Centos distro includes the OCFS2 module. Are
you using the modules downloaded from the oss.oracle.com site for the equivalent
RH 4.0 kernel, or modules built by Centos? If using CENTOS modules you might get
better results by changing to the Oracle built modules for the equivalent RH 4.0
kernel.
Regards,
Luis
Anjan Chakraborty <anjan.chakraborty@yahoo.com> wrote: Luis,
I am intending to use CRS/RAC that needs a Cluster File System. How does EXT3
falls into that area?
Thanks.
Anjan
Thanks a lot for the response. Here is what I am doing:
1.
mkfs.ocfs2 -b 4K -C 32K -N 4 -L ocrvotcrs /dev/sdb3 -- for CRS
mkfs.ocfs2 -b 4K -C 32K -N 4 -L orasys /dev/sdb4 -- for RDBMS
2. Then mounting using /etc/fstab:
/dev/sdb3 /home/oracle/ocrvotcrs ocfs2 _netdev,datavolume,nointr 0
0
/dev/sdb4 /home/oracle/orasys ocfs2 _netdev 0 0
If you find anything wrong here, can you please tell what to do?
It's a non-production system & so I can experiment with whatever you
suggest and won't held you responsible for that.
Thanks.
Anjan
Luis Freitas <lfreitas34@yahoo.com> wrote:
Anjan,
Are you installing the binaries on OCSF2 too? How are you mounting the
filesystem?
You might want to try using ext3 for the binaries and OCF2 only for datafiles
and archives, until you get this fixed.
Regards,
Luis
Anjan Chakraborty <anjan.chakraborty@yahoo.com> wrote: Hi,
I sent an email to Mark Fisheh of Oracle Corp. & posted this issue at OTN
under Linux thread this morning. I hope that someone among you might have
experienced this and can help. On that basis, I am sending this to you too. I am
stuck & will really appreciate if you can shed some light on this.
Thanks.
Anjan
***********************************************************************************************************
I have a 2 node CentOS 4.5 86_64 system (kernel 2.6.9-55.EL). On this I
installed Oracle OCFS2 1.2.7-1 (with exact kernel matching). After this I
installed Oracle CRS 10.2.0.1 and that installation went fine. Then I tried to
install Oracle RDBMS 10.2.0.1 and all the problems started from there. The
/var/log/messages file got filled up with messages (giving some to avoid
confusion):
ocfs2_read_locked_inode: .. : ERROR: Invalid dinode #0 signature ocfs2_lookup:
.. : ERROR: Unable to create inode ....
Then OUI gave several error messages, e.g.
.... Invalid stored block length on file ...../em/em.war followed by I/O error
in file
Errors in invoking to files ins_rdbms.mk and ins_ldap.mk
Then /var/log/messages gave:
OCFS2: ERROR (device ....): ocfs2_extend_file: Dinode # ...... has bad signature
O' # I ....
And the installation failed & CRS died. And the machines reboot.
I ran fsck.ocfs2 -n /dev/...., it came clean.
I have tested this several timnes & always same thing happening.
If I use RAW partitions, everything works fine. So, the problem may be in the
OCFS2 & OS/Oracle -- but, not sure how to bypass this.
I have to have OCFS2 -- can't use RAW for various reasons.
Can somebody please help me to resolve this?
Thanks.
***********************************************************************************************************
---------------------------------
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See
how._______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
oss.oracle.com/mailman/listinfo/ocfs2-users
---------------------------------
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.
---------------------------------
Never miss a thing. Make Yahoo your homepage.
---------------------------------
Get easy, one-click access to your favorites. Make Yahoo! your homepage.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
oss.oracle.com/pipermail/ocfs2-users/attachments/20071127/9d1546ad/attachment.html
On Mon, Nov 26, 2007 at 07:37:06AM -0800, Anjan Chakraborty wrote:> Hi, > I sent an email to Mark Fisheh of Oracle Corp. & posted this issue at OTN under > Linux thread this morning. I hope that someone among you might have experienced > this and can help. On that basis, I am sending this to you too. I am stuck & > will really appreciate if you can shed some light on this.Probably a lot of folks in the US were on vacation this last week. You should get better traction now since most of us are back :)> Thanks. > Anjan > *********************************************************************************************************** > I have a 2 node CentOS 4.5 86_64 system (kernel 2.6.9-55.EL). On this I > installed Oracle OCFS2 1.2.7-1 (with exact kernel matching). After this I > installed Oracle CRS 10.2.0.1 and that installation went fine. Then I tried to > install Oracle RDBMS 10.2.0.1 and all the problems started from there. The /var > /log/messages file got filled up with messages (giving some to avoid > confusion): > ocfs2_read_locked_inode: .. : ERROR: Invalid dinode #0 signature > ocfs2_lookup: .. : ERROR: Unable to create inode ....Are there any other types of messages on either node? The "Invalid dinode" message is very generic unfortunately, so typically we're looking for something before that to indicate a root cause.> Then OUI gave several error messages, e.g. > .... Invalid stored block length on file ...../em/em.war followed by I/O error > in file > Errors in invoking to files ins_rdbms.mk and ins_ldap.mk > > Then /var/log/messages gave: > OCFS2: ERROR (device ....): ocfs2_extend_file: Dinode # ...... has bad > signature O' # I .... > And the installation failed & CRS died. And the machines reboot. > I ran fsck.ocfs2 -n /dev/...., it came clean. > I have tested this several timnes & always same thing happening. > If I use RAW partitions, everything works fine. So, the problem may be in the > OCFS2 & OS/Oracle -- but, not sure how to bypass this. > I have to have OCFS2 -- can't use RAW for various reasons. > Can somebody please help me to resolve this?Can you describe your shared disk setup? Also, send me your cluster.conf files from all nodes. Considering it's a fresh file system and you've only just started putting files on it, my initial reaction is to check the shared disk. It could be that blocks are somehow being cached so the file system is getting stale or invalid meta data. I think Luis suggested trying an older version of Ocfs2. Feel free to do that, it could only add a potentially useful data point. You really don't have to jump far back though - just try 1.2.6 for starters. Thanks, --Mark -- Mark Fasheh Senior Software Developer, Oracle mark.fasheh@oracle.com
Maybe Matching Threads
- re: o2hb_do_disk_heartbeat:963 ERROR: Device "sdb1" another node is heartbeating in our slot!
- 6 node cluster with unexplained reboots
- Problem with OCFS2 on RHEL5.0 while installing CRS 10.2.01
- fs/ocfs2/super.c:1809 ocfs2_mount_volume() warn: missing error code 'status'
- Extended Attribute Support?