Re: [Nbd] nbd for large scale diskless linux -> tests & problem

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

Hi!!

> > So no much cpu consumption, but some of them waiting for IO. During bootup 
> > the servers gigabit link got up to 360MBits, little bit less with the 
> > "cat" ... With all the "cats" after a while around 230MBits ... A client
> > is still operable (graphical login into KDE) while cat is running. I 
> > have to purchase faster disks/and server memory now ...
>
> All very interesting, really. Would you object to me posting this story
> on the nbd homepage?

No problem at all :-)
 
> > I think nbd could be a real killer for nfs :-)
> > 
> > But I had a problem within my ramdisk setting up the nbd on some clients 
> > (dell 2,8Ghz P4, 1GB Ram, broadcom5700 gbit ethernet). I had to add a
> > "sleep 10" after powering up nbd-client server 5000 /dev/nb0 ...
> > Otherwise the system would crash because the device was not ready for
> > ext2 mount. It seems that the autoconfiguratin of the ethernet link
> > interupts the traffic and the nbd-client can not cope with that :-(
> 
> Hmm?
> 
> Is this an educated guess, or did you run some diagnostics that pointed
> you in this direction?

Just guess: The other machines I booted have via-rhine and e100 100Mbit 
chipsets. Maybe they do not any negotiation ... On the named machines
I get messages like: tg3 - 100Mbit full duplex set (or the way like
that)

> If the nbd-client gives control back to the parent process too fast,
> then that would be a bug in either nbd-client or the kernel. But I'd
> need some more info to be sure...

It is not easy to debug in initrd (rather restricted toolset) - I could
try to ping the machine from outside and see if any is interrupted or
run ethereal ...

Ciao,
	Dirk