[Nbd] Problems with nbd on SuSE10.0

[dsuchod <dsuchod@...65...>]

Hi!! After successfully using nbd on SuSE9.3 systems (2.6.11 kernel), I 
tried the same on SuSE10.0. Other then for 9.3 they provide a package
for nbd: rpm -qa nbd --> nbd-2.7.4-2

Unfortunately that one and a freshly compiled 2.8.1 from sources does
not work :-(

The nbd-2.7.4-2 could be started the normal way:

nbd-server 5000 /dev/sdb2 -r

nbd-client  10.8.4.254 5000 /dev/nbd0 (on the same machine)

but:
mount /dev/nbd0 /mnt
Error: Connection terminated: Connection reset by peer
mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 0
EXT3-fs: corrupt root inode, run e2fsck
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4128

The filesystem on that partition is OK, no errors with fsck. Same problems 
if I try to mount as ext2,3 option ro ...

proper shutdown of client: nbd-client -d /dev/nbd0
Disconnecting: queue, disconnect, clear, done.
hermes:/ # Error: Connection terminated: Broken pipe

does not work, I have to kill the client by hand.

Starting the new nbd-server generates an error message:

hermes:/tmp/nbd-2.8.1 # ./nbd-server 5000 /dev/sdb2 -r
E: The to be exported file needs to be an absolute filename!

I'm a little bit irritated if I'm doing something wrong, because all 
worked flawlessly for the older distro ... (I was using the 2.7.something 
version from sourceforge download ...)

my system: uname -a
Linux hermes 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 i686 i686 
i386 GNU/Linux

Any ideas!? 

	Dirk