Displaying 20 results from an estimated 1000 matches similar to: "RES: ocfs compilation error"
2004 Feb 02
1
ocfs compilation error
I'm trying to compile ocfs 1.0.9 and when I execute ./configure I receive
the following error msg:
*** the gtk-config script installed by GTK could not be found
*** If GTK wall installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GTK_CONFIG environmet variable to the
*** full path to gtk-config
configure: warning GTK+ not found, ocfstool will not be be built
when I run
2004 Feb 02
0
RES: RES: ocfs compilation error
Now it worked !!!!
Tks.
Mauro.
-----Mensagem original-----
De: bbarbe@ca-server1.us.oracle.com [mailto:bbarbe@ca-server1.us.oracle.com]
Em nome de Bert Barbe
Enviada em: Monday, February 02, 2004 5:04 PM
Para: Mauro Staretz
Assunto: Re: RES: [Ocfs-users] ocfs compilation error
oh and if you have a config.cache file in the source directory, it can help
to erase that before running configure
2004 Feb 06
0
ENC: RES: ocfs installation error on RHAS 2.1
Well, I've downloaded the kernel source code from
http://mirror.dulug.duke.edu/pub/redhat/linux/updates/enterprise/2.1AS/en/os
/SRPMS/kernel-2.4.18-e.40.src.rpm
and compiled it for x86 (i686).
Is this kernel compatible with ocfs ??
__________________________________________
Mauro Staretz - MI Montreal Inform?tica Ltda
Microsoft MCSE+I / MCDBA / MCP - Oracle OCP
Tel: 55-21-2291-6116 R.2104
2004 Feb 09
0
RES: RES: RES: ocfs installation error on RHAS 2.1
Well, I've compiled and installed Kernel 2.4.9-37 uniprocessor.
I've made ocfs setup using version 1.0.9-9 uniprocessor.
I've generated ocfs.conf using ocfstool.
When I start ocfs using /etc/init.d/ocfs start, I receive the following
errors:
[root@RAC1 root]# /etc/init.d/ocfs start
Loading OCFS: /sbin/insmod ocfs node_name=RAC1.localdomain
ip_address=192.168.61
2 ip_port=7000
2004 Feb 06
1
ocfs installation error on RHAS 2.1
I'm trying to install ocfs on a Redhat 2.1 AS, uniprocessor, kernel
2.4.18-e.40, and I'm receiving the following error message when I try to
install ocfs-support-1.0.9-12.i686.rpm:
Checking fir Red Hat enterprise kernel: [FAILED]
error: execution of %post scriptlet from ocfs-support-1.0.9-12, exit status
1
i've already installed those packages that are required for ocfs:
2004 Apr 30
1
ENC: ENC: Unresolved Symbols on Uniprocessor Kernel
As I said before, I'm not a linux expert.
In which file of kernel source can I look for any missing code ? And
specially what do I have to check ?
__________________________________________
Mauro Staretz - MI Montreal Inform?tica Ltda
Microsoft MCSE+I / MCDBA / MCP - Oracle OCP
Tel: 55-21-2291-6116 R.2104
Fax: 55-21-2533-6028
__________________________________________
-----Mensagem
2004 May 07
1
ENC: ENC: Unresolved Symbols on Uniprocessor Ker nel
Hi,
Is this "Unresolved Symbols" issue only occurring on VMware with e.38?
We have OCFS users want to update their kernel to e.34 or e.38 without
VMware.
Please advise, Thanks!
Roger---
-----Original Message-----
From: Wim Coekaerts [mailto:wim.coekaerts@oracle.com]
Sent: Friday, April 30, 2004 12:20 PM
To: Sunil Mushran
Cc: ocfs-users@oss.oracle.com
Subject: Re: ENC: ENC:
2004 Apr 30
1
ENC: Unresolved Symbols on Uniprocessor Kernel
I followed your instruction to compile OCFS and received the following
errors:
[root@RAC1 ocfs-1.0.11]# ./configure
--with-kernel=/usr/src/linux-2.4.9-e.38/linux
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are
2004 Apr 30
2
Unresolved Symbols on Uniprocessor Kernel
I'm trying to install ocfs using RHAS 2.1 uniprocessor kernel on a vmware
gsx server 3.0 virtual machine and I'm getting the unresolved symbols error
when I try to start ocfs.
I'm using the following packages:
ocfs-tools-1.0.10-1.i386.rpm
ocfs-support-1.0.10-1.i386.rpm
ocfs-2.4.9-e-1.0.11-1.i686.rpm
My kernel is 2.4.9-e.38 uniprocessor (compiled by me).
Questions:
1) Am I using the
2004 Feb 12
3
Ocfs mount issues
I am trying to mount the ocfs partitions using the following command
Mount -t ocfs -o uid=oracle,gid=dba /dev/sda /ocfs01 as user oracle and
group dba.
However it mounts the volume as root.
But if I use the ocfstool for the first and mount it as oracle:dba, the
subsequent mounts using the above command line mounts the volume as
oracle:dba.
Is there something that I am missing or I will have
2004 Mar 02
3
Odd errors while mounting an OCFS filesystem
Hello again. I am setting up a new pair of servers to run RAC.
They're connected via fibre-channel to a hardware RAID array, and both are
able to see the exposed LUNs.
When I create an OCFS filesystem on one node with mkfs.ocfs, I can
mount it. When I try to mount from the other node, however, it fails.
After that, the filesystem is left in a state where neither node can mount
it. The
2004 Jun 08
1
OCFS write/read across 2 nodes
Hi,
If I have ocfs on 2 nodes should I be able to do the following:
t=0
Node A
echo "1" > /ocfsmount/a
Node B
cat /ocfsmount/a
>>>>Question 1: At this point should I see "1"?
t=1
Node A
echo "2" > /ocfsmount/a
Node B
cat /ocfsmount/a
>>>>Question 2: At this point should I see
2004 Jun 29
1
seg fault using ocfstool
Hi all,
i have the following configuration:
RHAS 2.1 2.4.9-e.40enterprise #1 SMP (2 node cluster).
ocfs-support-1.1.2-1
ocfs-tools-1.1.2-1
ocfs-2.4.9-e-enterprise-1.0.12-1
i followed the users guide to install and configure ocfs.
During definition and formatting of ocfs-partitions the ocfstool crashed.
Now restarting ocfstool fails with the following error:
ocfstool
Abnormal termination!
2004 Aug 23
2
Changing a node's hostname.
What steps do I need to take to change a host's name? I modified the
/etc/ocfs.conf file but ocfstool still reports the old name under the
"Configured Nodes" tab.
I'm also wondering where ocfstool stores the partition information that
it shows under the device list. I dumped a couple ocfs partitions but
they still show up in ocfstool.
Thanks, Don
2004 Mar 05
1
Worrisome file listings in ocfstool
We finally seem to have worked most of the kinks out of our OCFS/RAC
setup, and are running a mass import to clone our production database for
testing.
While this has been going on, I fired up ocfstool to check out the
states of the various shared volumes. In several cases, I saw (in the File
Listing tab) multiple entries for some directories and files at the
filesystem root. The duplicate
2004 Apr 21
1
Fwd: RE: OCFS Hang
Oh yeah - easy way to check, Randy:
Next time your node hangs, get on the OTHER NODE and go into each
directory where files are being opened (datafiles, archivelogs,
controlefiles, redo logs, etc) and delete a file (you can create one
first then delete it). If this causes the hung node to recover then
you're having the same problem I was having.
Jeremy
>>> "Jeremy
2004 Jun 18
2
Problems with OCFSTOOL after LUN Maintenance
In installing 10g\RAC we hit an issue that has been indentified as a bug
with CRS where the cluster locking files cannot be implemented under
OCFS. Supposedly they work fine when implemented as Raw Devices.
We needed to reclaim some space from existing LUN's to create the raw
devices as we had expected to able to put all Oracle related files under
OCFS (Yes, we belived the hype). This
2003 Aug 11
1
Strange "feature"
Hi all!
Doing my first steps with OCFS (1.0.9), I ran across a nifty little
"feature"....
We've been trying if DMP with QLogic 2300 HBAs works without having DMP
activated (ok, blame on me...).
ocfstool allows you to mount different partitions on the same mountpoint, but
after we tried that, everything went to state "D" and we chose to reboot the
whole cluster (4
2018 Jan 02
1
"file changed as we read it" message during tar file creation on GlusterFS
Hi Ravi,
thank you very much for your support and explanation.
If I understand, the ctime xlator feature is not present in the current gluster package but it will be in the future release, right?
Thank you again,
Mauro
> Il giorno 02 gen 2018, alle ore 12:53, Ravishankar N <ravishankar at redhat.com> ha scritto:
>
> I think it is safe to ignore it. The problem exists due to the
2018 Jan 02
0
"file changed as we read it" message during tar file creation on GlusterFS
I think it is safe to ignore it. The problem exists? due to the minor
difference in file time stamps in the backend bricks of the same sub
volume (for a given file) and during the course of tar, the timestamp
can be served from different bricks causing it to complain . The ctime
xlator[1] feature once ready should fix this issue by storing time
stamps as xattrs on the bricks. i.e. all bricks