Possible EON vs FreeNas comparison

[00Roush]

It sounds like you are missing and argument. To test a destroy on a pool with name test
you would type
zpool destroy test
or with the force switch (try to limit this use to only when necessary)
zpool destroy -f test

as a safe measure you should always try to unmount the pool to stop any possible I/O operations
zfs unmount -a
then zpool destroy test

Well I meant to say that I have been using the zpool destory command on a certain pool. For example zpool destory thing and I get the error with the argument list. Same goes when I use zpool destory -f thing. Thing still shows up when I do zpool list.

00Roush

 

[eon]

Sounds odd

If you can login through ssh and post back a text scrape of the ssh output or screenshot.

Thanks

 

[00Roush]

If you can login through ssh and post back a text scrape of the ssh output or screenshot.

Thanks

Don't mind me... I NEED TO LEARN HOW TO SPELL. The destroy command works just fine.

So besides that do you know if there is a driver I can install so my Marvell Yukon 88E8053 PCIe network card will work? Well actually Marvell has a Solaris driver on their website. http://www.marvell.com/drivers/driverDisplay.do?driverId=180 I am just unsure how I can install this driver on EON. (or if it would work) From what I can tell pkgadd is not available in the basic EON installation. I did see a blog you posted about adding drivers but I didn't really want to mess with it until I asked you.

00Roush

 

[dje007]

Unable to install via USB dvd drive, gets to the 1st stage of the grub loader then hangs

 

[eon]

00Roush,

I will take at a look but at a glance it only contains the 64 bit driver, no 32-bit driver. You are using the 32 bit image right? If so then this driver won't work with the 32-bit image. Great find btw.

dje007,

It's probably easier to try another drive. The CD/DVD is only needed for boot and install after that its all the usb or CF key.

Hanging at grub is weird. Try booting in verbose mode and see. Please search back this post for guidance how to boot in various modes.
press e at splash and change unix to unix -m verbose or unix -v

 

[dje007]

Hanging at grub is weird. Try booting in verbose mode and see. Please search back this post for guidance how to boot in various modes.
press e at splash and change unix to unix -m verbose or unix -v[/QUOTE]


Stage one you don't get the splash screen that is stage two but thanks.

 

[00Roush]

00Roush,

I will take at a look but at a glance it only contains the 64 bit driver, no 32-bit driver. You are using the 32 bit image right? If so then this driver won't work with the 32-bit image. Great find btw.

I am using the EON 64 bit SAMBA build. Actually Marvell looks to have support for quite a few OSes. Here is the link to the driver search... http://www.marvell.com/drivers/search.do

00Roush

 

[eon]

adding the marvell yukon driver manually

00Roush,

transfer the file to somewhere on preferably on a zpool. In my case /pool
unzip the package
gzip -dc yukonxsol_x64v10.0.3.3.tar.Z | tar -xf -
cd YUKONXsolx/reloc/kernel/drv
copy the conf file to its proper location (lot of features in this conf to play with but I loaded its default unedited)
cp yukonx.conf /kernel/drv/
cd amd64/
copy the 64 bit driver to its proper location
cp yukonx /kernel/drv/amd64/

now lets load/test the driver
cd /kernel/drv/amd64/
add_drv -v yukonx
view driver status
modinfo -c | grep yukon

It should have also added an entry to /etc/name_to_major (in my case it added)
yukonx 65

if the driver is working and you wish to commit the changes to the boot image
edit /mnt/eon0/.backup and add
/kernel/drv/yukonx.conf
/kernel/drv/amd64/yukonx
/etc/name_to_major

run updimg.sh and the next time you reboot it should be working. This card supports vlan and other features see the following for more details
/pool/YUKONXsolx/reloc/usr/sbin/yukonx_vlan_config
/pool/YUKONXsolx/reloc/etc/rcS.d/S50yukonx

 

[00Roush]

Well I got as far as this section...

"if the driver is working and you wish to commit the changes to the boot image
edit /mnt/eon0/.backup and add
/kernel/drv/yukonx.conf
/kernel/drv/amd64/yukonx
/etc/name_to_major"

/mnt/eon0 is mounted as read only so I cannot modify the .backup file using vi.

/mnt/eon3/.backup looks like it can be modified but I am guessing it would not work.

00Roush

 

[eon]

00Roush,

It shouldn't be read only, sound like the USB is mounted 3rd/4th? Is it possible you still have the CD in the drive? If so remove and boot only with the USB or kindly paste the output of df -h

Thanks

 

[00Roush]

Well I was booting from a hard disk but still had the cd in the drive for a while. I wiped everything then did a fresh install and removed the cd and was able to finish the driver install. I did run into some problems getting the driver to work though. Had to use this command line to add the driver... add_drv -m '* 0660 root sys' -i '"pci11ab,4320" "pci11ab,4340" "pci11ab,4341" "pci11ab,4342" "pci11ab,4343" "pci11ab,4344" "pci11ab,4345" "pci11ab,4346" "pci11ab,4347" "pci11ab,4350" "pci11ab,4351" "pci11ab,4352" "pci11ab,4353" "pci11ab,4354" "pci11ab,4355" "pci11ab,4357" "pci11ab,435a" "pci11ab,4360" "pci11ab,4361" "pci11ab,4362" "pci11ab,4363" "pci11ab,4364" "pci11ab,4365" "pci11ab,436b" "pci11ab,436c" "pci11ab,4369" "pci11ab,4370" "pci11ab,4380" "pci1148,9e00" "pci1148,9000" "pci1148,5021" "pci1148,5041" "pci1148,5043" "pci1148,5051" "pci1148,5061" "pci1148,5071" "pci1148,3221" "pci1148,9521"' yukonx. This is what was mentioned in the readme file included with the driver. Once I did that the network cards in my computer were recognized. Those step by steps really helped out as well.

I will do some more testing and see what kind of performance I can get now.

00Roush

 

[00Roush]

Sorry it took so long to post back on this thread.

My results with using the onboard Marvell PCIe based network card have been mixed. Write speeds to the server seem to be better than the Intel PCI network card and are around 90-100 MB/sec. Read speeds for some reason are basically the same. Maybe just a little higher at around 65 MB/sec. I know the setup is capable of higher performance as EON has the reported the drive speed at 100 MB/sec. CPU usage looks to be around 25% on just one of the CPU's so I don't think I am hitting a bottleneck there. Any thoughts or anything you might want me to check. So far I have not tried jumbo frames.

On a side note I haven't figured out to properly setup the Marvell network card so that it works on a reboot. When I reboot it does not seem to detect the card so I have to manually remove the driver then add it again with the previously posted command line. Then set it up using ifconfig. Any way you might be able to include the Marvell driver in a future EON revision.

00Roush

 

[eon]

Hi 00Roush,

No worries. I've been getting hammered at work. I will definitely look into adding the yukon driver in the upcoming release. I am waiting for snv_118 as I'm seeing some quirks in snv_117 that I hope they fix for 118.

I'd have to look into why it's not properly loading at boot.

I was looking for some kind of side by side comparison with freenas or some performance charting like ones done for the some of the units reviewed.

example:
http://www.smallnetbuilder.com/content/view/30179/75/1/5/

thanks

 

[00Roush]

I will do some performance testing with FreeNAS and then get some performance charts together. I am thinking I will use the latest stable i386 build of FreeNAS against the EON 32 bit SAMBA build for the charts. Probably will end up testing the 64 bit versions as well just to see if there is a difference. I'll let you know how it turns out.

00Roush

 

[pxu]

00Rush, I have a shuttle k45 with a marvell gigabit and have the exact same issue. I found your add_drv -m command added the pci11ab entries to the /etc/driver_aliases file. I then follow the directions from eon, and added the file to .backup, once I updated the image, network came up successfully after the reboot. Also, upon saving .backup, it gave me the read-only warning, I had to force write :w! in vi, important bit of info for us that don't use linux/unix.

edit /mnt/eon0/.backup and add
/kernel/drv/yukonx.conf
/kernel/drv/amd64/yukonx
/etc/name_to_major
/etc/driver_aliases <--- 00Rush's add_drv -m command added all the pci11ab,#### entries to this file

ran updimg.sh, reboot and network was working.

Thanks eon for this great mini zfs distro, can't wait for your future releases.

 

[eon]

Thanks for trying and info.

pxu,

Thanks for the info and taking the time to try it. I am waiting for snv_118 to make the next release. snv_117 adds autoexpanding to zfs allowing you to upgrade the size of pools originally built with 500GB for example to 1 TB disks but it has zfs mount race bug with tiered filesystems.

I hope this will be fixed in snv_118. We may see the long awaited deduplication feature in 118 too!

 

[00Roush]

00Rush, I have a shuttle k45 with a marvell gigabit and have the exact same issue. I found your add_drv -m command added the pci11ab entries to the /etc/driver_aliases file. I then follow the directions from eon, and added the file to .backup, once I updated the image, network came up successfully after the reboot. Also, upon saving .backup, it gave me the read-only warning, I had to force write :w! in vi, important bit of info for us that don't use linux/unix.

edit /mnt/eon0/.backup and add
/kernel/drv/yukonx.conf
/kernel/drv/amd64/yukonx
/etc/name_to_major
/etc/driver_aliases <--- 00Rush's add_drv -m command added all the pci11ab,#### entries to this file

ran updimg.sh, reboot and network was working.

Thanks eon for this great mini zfs distro, can't wait for your future releases.

That worked great! Thanks.

00Roush

 

[00Roush]

I finally got around to making some charts. Testing has been a little hard... I have been unable to get consistent results with EON. I originally wanted to test the EON 32 bit SAMBA version against the standard FreeNAS version but my results with EON were not really up to par. So I ended up using the EON 64 bit SAMBA version for testing as performance was better but still the results were not consistent. Well I should say write results were not consistent as my read speeds seemed to be about the same even adding another hard drive. I decided to show my average EON results as well as the best write results.

I want to note that on both FreeNAS and EON I changed the send and receive buffer sizes to 65536 for SAMBA.

http://i293.photobucket.com/albums/mm60/dmaster520/readspeed-1.jpg

http://i293.photobucket.com/albums/mm60/dmaster520/writespeed-1.jpg

http://i293.photobucket.com/albums/mm60/dmaster520/bestwritespeed.jpg

First thing I noticed was that FreeNAS .69 had pretty good read and write speeds on my hardware. For some reason .7 RC1 had much slower read speeds... not sure why.

With that said I really do think that with EON performance was being held back by something. First thing I noticed when writing to the EON server was that the network traffic was pausing. When I looked at the stats in Vista I could see that data was blasting across the network at around 100-110 MB/sec for a few seconds and then it would stop for a second or so. This would go on for the whole file copy. On the writes that gave the best results this would not happen at all or would only happen a couple of times. It never seemed to be consistent... I would do one file copy that was blazing fast then move onto the next and it would crawl along pausing every couple of seconds. I mentioned in a previous post in this thread about needing to change from AHCI mode to IDE mode... Maybe that has something to do with it.

I think next I might give OpenSolaris Express a go. I tried the standard OpenSolaris live CD and it would load but then would come up with some IDE error. So maybe my hardware is not completely supported.

On a side note... Would you be able to add Iperf to EON? Just helps out when trying to diagnose where a bottle neck might be.

00Roush

 

[eon]

Hi 00Roush, thanks for your time and efforts

I will take a look at your results and and see if I can fill the shortfalls. A n ew version was released today http://eonstorage.blogspot.com/

 

[00Roush]

I will take a look at your results and and see if I can fill the shortfalls. A n ew version was released today http://eonstorage.blogspot.com/

Sweet! When I get a chance I will give it a go.

00Roush