[ENBD] nbd 2.4.27 recommended kernel
Cicero Mota
enbd@lists.community.tummy.com
Tue, 12 Mar 2002 20:04:49 -0400
Dear Peter,
Here is what I did, hope you can give some help
Cicero
dd if=/dev/zero of=/tmp/delme bs=1024 count=5000000
# /tmp/nbd-server 1025 /tmp/delme
fourier:/tmp # nbd-server 2597: main server (-2) cannot find nbd-cstatd in
/etc/services
nbd-server 2597: server (-2) set new signal handlers for master server 2597
# insmod /tmp/nbd.o
# /tmp/nbd-client localhost:1025 -n 1 /dev/nda
server output was ok, I think:
nbd-server 2597: server (-2) opened port 1025 (socket 1) for client 127.0.0.1
nbd-server 2608: server (-1) set default signal handlers for session server
2608
nbd-server 2608: server (-1) read passwd ok
nbd-server 2608: server (-1) got cliserv magic ok
nbd-server 2608: server (-1) received id device 2b00 ok
nbd-server 2608: server (-1) sent size 505614336 ok
nbd-server 2608: server (-1) sent sig ok
nbd-server 2608: server (-1) suggested ro flags 0 ok
nbd-server 2608: server (-1) received blksize 1024 ok
nbd-server 2608: server (-1) sent/negotiated blksize 1024 ok
nbd-server 2608: server (-1) received pulse_intvl 10 ok
nbd-server 2608: server (-1) sent/negotiated pulse interval 10 ok
nbd-server 2608: server (-1) agreed 1 channels ok
nbd-server 2608: server (-1) selected free port at 1026
nbd-server 2608: server (-1) posted port 1026 ok
nbd-server 2608: server (-1) manager started new process group 2608
nbd-server 2610: server (0) set default signal handlers for slave server 2610
nbd-server 2610: server (0) opened port 1026 (socket 6) for client 127.0.0.1
nbd-server 2610: server (0) set new signal handlers for slave server 2610
nbd-server 2610: newproto net errored on packet. Breaking off.
nbd-server 2608: server (-1) set new signal handlers for session server 2608
nbd-server 2610: slavesighandler server (0) activates slave sighandler for
signal 15
nbd-server 2610: server (0) sighandler terminates slave 2610 safely
nbd-server 2608: server (-1) relaunches child after SIGCHLD
nbd-server 2608: server (-1) slave pid 2610 is down, launching new
nbd-server 2611: server (0) set default signal handlers for slave server 2611
nbd-server 2608: server (-1) launched slave pid 2611
client output also was ok:
nbd-client 2606: client (-1) manager opened NBD device /dev/nda (2b00)
nbd-client 2606: client (-1) set kernel bdflush sync boundary to 80% from 60%
nbd-client 2606: client (-1) set kernel bdflush async boundary to 25% from
30%
fourier:~ # nbd-client 2607: client (-1) starts introduction sequence on
port 1025
nbd-client 2607: client (-1) got session port 1026 ok
nbd-client 2607: client (-1) introduction sequence ends ok
nbd-client 2609: ok
nbd-client 2609: client (0) opened socket 5 to port 1026
nbd-client 2609: client (0) read passwd ok from port 1026
nbd-client 2609: client (0) got cliserv magic ok from port 1026
nbd-client 2609: client (0) got a signature ok from port 1026
nbd-client 2609: client (0) begins main loop
and then
#mke2fs /dev/nda
mke2fs 1.24a (02-Sep-2001)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
123464 inodes, 493764 blocks
24688 blocks (5.00%) reserved for the super user
First data block=1
61 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
Writing inode tables: done
Segmentation fault
^^^^^^^^^^^^^^^
Output in /var/log/messages
Mar 12 19:33:54 fourier nbd-server: size of exported file/device is 505614336
Mar 12 19:38:20 fourier kernel: NBD #5318[0]: nbd_init Network Block Device
support by pavel@elf.mj.gts.cz
Mar 12 19:38:20 fourier kernel: NBD #5319[0]: nbd_init Network Block Device
port to 2.0 by ptb@it.uc3m.es
Mar 12 19:38:20 fourier kernel: NBD #5320[0]: nbd_init Network Block Device
move networking to user space by amarin@it.uc3m.es
Mar 12 19:38:20 fourier kernel: NBD #5322[0]: nbd_init Enhanced Network Block
Device 2.4.27 $Date$ by ptb@it.uc3m.es
Mar 12 19:38:20 fourier kernel: NBD #5333[0]: nbd_init registered device at
major 43
Mar 12 19:41:34 fourier kernel: NBD #2765[0]: nbd_set_sock setting unsigned
device nda! But harmless.
Mar 12 19:41:34 fourier kernel: NBD #2824[0]: nbd_set_sock increased socket
count to 1
Mar 12 19:41:34 fourier kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000a33
Mar 12 19:41:34 fourier kernel: printing eip:
Mar 12 19:41:34 fourier kernel: c0114528
Mar 12 19:41:34 fourier kernel: *pde = 00000000
Mar 12 19:41:34 fourier kernel: Oops: 0002
Mar 12 19:41:34 fourier kernel: CPU: 0
Mar 12 19:41:34 fourier kernel: EIP:
0010:[interruptible_sleep_on_timeout+44/104]
Mar 12 19:41:34 fourier kernel: EFLAGS: 00210086
Mar 12 19:41:34 fourier kernel: eax: 00000a2f ebx: 00200286 ecx: c4ccac28
edx: c5779f00
Mar 12 19:41:34 fourier kernel: esi: 000003e8 edi: c4cca3b0 ebp: c5779f08
esp: c5779ef0
On Tuesday 12 March 2002 12:05, you wrote:
> "A month of sundays ago Cicero Mota wrote:"
>
> > is there a recommended linux kernel for nbd 2.4.27?
> > is there some reason why it should no work with linux 2.4.10?
>
> Yep. Plenty. For one I never tested it with 2.4.10. For another I
> could never boot 2.4.10 stably on my machine (I think I managed it
> once). I did test with 2.4.8 and 2.4.9 during development, but I don't
> recall if I retested the final release on them. I did most of the
> development under 2.4.8 and 2.4.17rc2. And 2.4.13+ have a completely
> different memory manager.
>
> Can you be specific about the problem? If it's a compile problem, that
> should be easily fixable, and I'd like to know about it.
>
> Peter
> _______________________________________________
> ENBD mailing list
> ENBD@lists.community.tummy.com
> http://lists.community.tummy.com/mailman/listinfo/enbd