Compiling module problems...

Chen,

As you told me, here you have the errors I got when trying to compile
the intermezzo module from the ./fs24 directory from the
intersync-0.9.5-3 source package.

The "./configure" command runs with no problem.
When I do a "make", it breaks when it gets to this point:

--BEGIN--
gcc  -I. -I.   -I.  -I/usr/src/linux/include  -D__KERNEL__ -DMODULE
-g -O2 -Wall -Wstrict-prototypes -pipe -DMODULE -DMODVERSIONS -include
/usr/src/linux/include/linux/modversions.h -DEXPORT_SYMTAB -c `test -f
'presto.c' || echo './'`presto.c
In file included from /usr/src/linux/include/asm/semaphore.h:39,
                 from /usr/src/linux/include/linux/fs.h:200,
                 from /usr/src/linux/include/linux/capability.h:17,
                 from /usr/src/linux/include/linux/binfmts.h:5,
                 from /usr/src/linux/include/linux/sched.h:9,
                 from presto.c:27:
/usr/src/linux/include/asm/system.h: In function `__set_64bit_var':
/usr/src/linux/include/asm/system.h:190: warning: dereferencing
type-punned pointer will break strict-aliasing rules
/usr/src/linux/include/asm/system.h:190: warning: dereferencing
type-punned pointer will break strict-aliasing rules
presto.c: In function `presto_get_permit':
presto.c:464: error: structure has no member named `parent'
presto.c:464: error: structure has no member named `parent'
presto.c: In function `presto_put_permit':
presto.c:575: error: structure has no member named `parent'
presto.c:575: error: structure has no member named `parent'
presto.c: In function `presto_is_read_only':
presto.c:735: error: structure has no member named `parent'
presto.c:735: error: structure has no member named `parent'
presto.c:738: error: structure has no member named `parent'
presto.c:738: error: structure has no member named `parent'
make[1]: *** [presto.o] Error 1
make[1]: Leaving directory `/root/src/intersync-0.9.5/fs24'
make: *** [all-recursive] Error 1
--END--

Actually, these two messages:
--BEGIN--
/usr/src/linux/include/asm/system.h: In function `__set_64bit_var':
/usr/src/linux/include/asm/system.h:190: warning: dereferencing
type-punned pointer will break strict-aliasing rules
/usr/src/linux/include/asm/system.h:190: warning: dereferencing
type-punned pointer will break strict-aliasing rules
--END--

get repeated all the time, for every source file.
The only difference is when it gets to compile this last file, apart
from these messages, it crashes as you can see.


If it helps, here you have the "./configure" output:
--BEGIN--
root@tgn2 ~/src/intersync-0.9.5/fs24# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i586-pc-linux-gnu
checking host system type... i586-pc-linux-gnu
checking target system type... i586-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 cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking if make dep has been run in kernel source... yes
checking if autoconf.h is in kernel source... yes
checking if you are running user mode linux for ..... no
checking setting make flags system architecture: ... i586
checking for MODVERSIONS... yes
checking for SMP... no
checking for Linux release... 2.4.21-15tr
configure: creating ./config.status
config.status: creating Makefile
config.status: creating linux/Makefile
config.status: executing depfiles commands
--END--


Hope this helps you somehow.
Do you need any other info about my system??
Running TSL2.0 (RedHat based) distro. Kernel 2.4.21, no SMP.


Bye,


--
Josep Maria Torné Fernàndez
jm.torne@xxxxxxxxxxxxxxx
Responsable Departament d'Informàtica i Comunicacions
TSI (Tarragona Sistemes Industrials, SL) 
http://www.infor.tgnsi.com/
43006 - TARRAGONA (SPAIN)

-----Mensaje original-----
De: intermezzo-discuss-admin@xxxxxxxxxxxxxxxxxxxxx
[mailto:intermezzo-discuss-admin@xxxxxxxxxxxxxxxxxxxxx] En nombre de
Yang, Chen
Enviado el: domingo, 16 de noviembre de 2003 16:13
Para: Josep M. Torné Fernàndez; intermezzo-discuss@xxxxxxxxxxxxxxxxxxxxx
Asunto: Re: First tests with Intermezzo... not very encouraging :(

Hi, Joesp:
     Thanks for your step by step setup process description.
     To your problem, Would you like to use the code in fs24 directory
with
the intersync-0.9.5-3.rpm?
I am not sure of the kernel module would work with current intersync
since
the most updated version for fs24 is with the intersync distrobution. I
once
heard from you that you have problem compiling it with linux kernel
2.4.21,
would you like to tell me what the concrete problems are? I have tested
it
with Redhat 9, it works.
     Thanks.
--
     Yang, Chen
----- Original Message ----- 
From: "Josep M. Torné Fernàndez" <jm.torne@xxxxxxxxxxxxxxx>
To: <intermezzo-discuss@xxxxxxxxxxxxxxxxxxxxx>
Sent: Sunday, November 16, 2003 1:36 AM
Subject: First tests with Intermezzo... not very encouraging :(


Hi,

After getting an intermezzo setup to work this morning, I've decided to
perform some tests to check would intermezzo would fit to my
environment.

Environment description:
Two servers, with 40Gb HDD each one. They both have a 30Gb partition to
use with intermezzo. Both servers are linked with a cross-over cable.
Both running same distro, TSL2.0 with kernel 2.4.21 and intermezzo
kernel module that came with the distro.
I'm running intersync like "intersync --debug 1 /export" to check
messages generated by intersync.

Tests (extremely simple anyway)
- "touching" files on first on client and seeing how they populate to
server (test OK)
- now on server seeing how the populate to client (test OK)
- now I decide to "cat" and "more" files on the server (test OK)
- now I "cat" and "more" files on the client: PROBLEMS!!

Sporadically, "cat" or "more" crashes with a "segmentation fault". It
seems that mostly when first accessing some files, but not always and
not for all the files.

Here you have the sequence of messages:
1) When I try to "cat" files (zero length files, as I created them with
the "touch" command) like this:

--BEGIN
root@tgn2 /export2# more rerewrewr
Segmentation fault
root@tgn2 /export2# mor rerewrewr
-bash: mor: command not found
root@tgn2 /export2# more rerewrewr
root@tgn2 /export2# cat rerewrewr
root@tgn2 /export2# ls
junaito  pepe  pepepepe  rerewrewr
root@tgn2 /export2# cat pepe
root@tgn2 /export2# cat juanito
cat: juanito: No such file or directory
root@tgn2 /export2# ls
junaito  pepe  pepepepe  rerewrewr
root@tgn2 /export2# cat junaito
Segmentation fault
root@tgn2 /export2# cat junaito
root@tgn2 /export2# ls
junaito  pepe  pepepepe  rerewrewr
root@tgn2 /export2# dd if=/dev/zero of=tmp.tmp.tmp bs=1024 count=10000
10000+0 records in
10000+0 records out
--END--
The file names do exist. On the bellow log generated by the CLIENT the
"segmentation faults" seem to coincide with the "JOB_BACKFETCH failed,
rc: 2" messages on the CLIENT log:
--BEGIN--
root@tgn2 /usr/lib# intersync --server="10.9.8.2" --debug 1 /export2/
(fileset.c:is_cache_initialize L729): cache /export2 ----- channel 0
(connecting.c:is_peer_new L59): setting up new peer 208090a port 370
(request.c:is_get_uuid L534):
(request.c:is_get_uuid L555): body: bee35501-961e-465d-b55b-805d33742714
(fileset.c:is_client_init_fset L563): Initializing fset: rootfset
(fileset.c:is_fileset_new L309): setting up new fileset rootfset dir
/export2/.intermezzo/rootfset/ROOT
is_client_init_fset: data_on_demand: 1
(session.c:is_run_context L138): get_last_rcvd: kml offset: 0
(session.c:is_run_context L141): izo_ioc_get_rcvd failed: Invalid
argument
(upcall.c:upc_dispatch L374): Permit given to peer 0x8067760
(session.c:is_run_context L201): get fileid
(request.c:is_get_fileid L595): fileid response: 'f:da90dcd770'
(request.c:is_get_fileid L605): setting fileid
/export2/.intermezzo/rootfset/ROOT:/rerewrewr, f:da90dcd770
(request.c:is_get_fileid L607): setting fileid status 0
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: 2
(session.c:is_run_context L201): get fileid
(request.c:is_get_fileid L595): fileid response: 'c:da90dcd4in1'
(request.c:is_get_fileid L605): setting fileid
/export2/.intermezzo/rootfset/ROOT:/pepe, c:da90dcd4
(request.c:is_get_fileid L607): setting fileid status 0
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L201): get fileid
(request.c:is_get_fileid L595): fileid response: 'd:da90dcd570'
(request.c:is_get_fileid L605): setting fileid
/export2/.intermezzo/rootfset/ROOT:/junaito, d:da90dcd570
(request.c:is_get_fileid L607): setting fileid status 0
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: 2
--END--
Finally, when I try the last command on the CLIENT show above (the "dd"
command) the CLIENT intersync log doesn't show any error message, but
instead the SERVER complains and crashes:
--BEGIN--
root@tgn1 ~# intersync --debug 1 /export/
(fileset.c:is_cache_initialize L729): cache /export ----- channel 0
(fileset.c:is_build_fileset L420): Initializing fileset "rootfs"
(fileset.c:is_fileset_new L309): setting up new fileset rootfs dir
/export/.inte
(fileset.c:is_build_fileset L420): Initializing fileset "rootfset"
(fileset.c:is_fileset_new L309): setting up new fileset rootfset dir
/export/.in
(connecting.c:is_peer_new L59): setting up new peer 108090a port 2432
(request.c:is_get_uuid L534):
(request.c:is_get_uuid L555): body:
bc5ba5c6-751a-42bd-9eb2-7e72e3ad69b5Ù
(upcall.c:upc_dispatch L374): Permit given to peer 0x806acd0
(upcall.c:upc_dispatch L374): Permit given to peer 0x806acd0
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(session.c:is_run_context L194): doing backfetch
(session.c:is_run_context L242): JOB_BACKFETCH failed, rc: -1
(request.c:is_get_kml_range L277) ABORT: reintegrate failed, aborting:
Operation not permitted
--END-- 

I wouldn't say I have stressed intermezzo too much, but it doesn't seem
to be able to handle such simple tests. Am I doing something wrong??

I was looking for a distributed filesystem for my production servers,
but I don't think I can use intermezzo at the moment.
I'll just start looking for other DFS and just keep testing intermezzo
whenever I have time on the future. I have to confess that it's a real
pity, as I just loved the simplicity and easy of use of intermezzo
compared to other DFS, like for example CODA, which I've also considered
as the DFS to use in the past, but discarded because of the, in my
opinion, not-trivial setup and administration tasks.


Anyway, thanks again to everybody,


--
Josep Maria Torné Fernàndez
jm.torne@xxxxxxxxxxxxxxx
Responsable Departament d'Informàtica i Comunicacions
TSI (Tarragona Sistemes Industrials, SL)
http://www.infor.tgnsi.com
43006 - TARRAGONA (SPAIN)




-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=/g22lp.tmpl
_______________________________________________
intermezzo-discuss mailing list
intermezzo-discuss@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/intermezzo-discuss



-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
intermezzo-discuss mailing list
intermezzo-discuss@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/intermezzo-discuss



-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl