[ENBD] More nbd-2.4.1 questions on kernel 2.2.18

[Kai Chen]

Hi! Peter,

>Most certainly you are mistaken. That is a prerequisite, not a
>symptom.

I did do "make config all."

And during the compilation, I did see things like:

gcc -O2 -Wall -D_LARGEFILE64_SOURCE -I/home/kylechen/nbd-2.4.21/tmp 
-I/home/kylechen/nbd-2.4.21/linux/include  -DDEBUG=0 -o nbd-server.o -c 
/home/kylechen/nbd-2.4.21/nbd/nbd-server.c
gcc -O2 -Wall -D_LARGEFILE64_SOURCE -I/home/kylechen/nbd-2.4.21/tmp 
-I/home/kylechen/nbd-2.4.21/linux/include  -DDEBUG=0 -o socket.o -c 
/home/kylechen/nbd-2.4.21/nbd/socket.c
gcc -O2 -Wall -D_LARGEFILE64_SOURCE -I/home/kylechen/nbd-2.4.21/tmp 
-I/home/kylechen/nbd-2.4.21/linux/include  -DDEBUG=0 -o logging.o -c 
/home/kylechen/nbd-2.4.21/nbd/logging.c
gcc -O2 -Wall -D_LARGEFILE64_SOURCE -I/home/kylechen/nbd-2.4.21/tmp 
-I/home/kylechen/nbd-2.4.21/linux/include  -DDEBUG=0 -o alarm.o -c 
/home/kylechen/nbd-2.4.21/nbd/alarm.c
gcc -O2 -Wall -D_LARGEFILE64_SOURCE -I/home/kylechen/nbd-2.4.21/tmp 
-I/home/kylechen/nbd-2.4.21/linux/include  -DDEBUG=0 -o file.o -c 
/home/kylechen/nbd-2.4.21/nbd/file.c
gcc -O2 -Wall -D_LARGEFILE64_SOURCE -I/home/kylechen/nbd-2.4.21/tmp 
-I/home/kylechen/nbd-2.4.21/linux/include  -DDEBUG=0 -o select.o -c 
/home/kylechen/nbd-2.4.21/nbd/select.c

So I think that part should be fine.

What I was wondering about was if I should have done something to, e.g., the 
kernel to support these "large files?"

>And may I add "please remove config.cache". Since these are snapshots, 
>taken automatically, I may well have accidently caught a local config.cache 
>in them!

I didn't see "config.cache," but I did "make clean" and "make ditclean," so 
I think the configuration cache was removed.

The same out of range problem is still there, like before, as follows:

>>nbd-client-server: writenet exits FAIL
>>file: Can not seek locally to offset 2147483648!
>
>I suspect that you really haven't run make config. At least look in 
>config.h and see if the configured values are appropriate for your system.

I'm attaching my config.h file at the end of this message.

>>nbd/fileserver: short read to buffer offset 0, wanted 4096 got -22
>>
>>The client sometimes did stop.  It shows:
>>
>>nbd-client-netserver: client (0) short read from net to buffer  offset 0, 
>>wanted 4096 got -110
>
>That's saying it couldn't even succeed in negotiating the handshake.
>The mkfs would never have run.

Unfortunately "mkfs" did run successfully even with the above error 
messages.

>That's often a symptom of completely mismatched systems. Such as
>compiling on a redhat 7 system and then trying to run on a redhat 6
>or older.

I'm running Redhat 6.2 with kernel 2.2.18 everywhere.  There should be no 
mismatch...

I use PIII 800 128M RAM with both SCSI and Fibre Channel Drives as my 
server.  The clients are PIII's or Celeron's.

Please advise.  Many thanks.

Kyle
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com