You have probably noticed xsconf.program (eg xsconf.rsync) name in the download section and wondered how it's used? Here's a video that will hopefully answer that and help if you wish to compile your own binaries (eg rsync) or other open source packages. The notes.program name (eg notes.rsync) contains where to get the source code and any notes/tips/edits needed for a successful compile. A pre-requisite for this exercise is a sunstudio 12 and/or gcc compiler. After the compilers are downloaded and installed on a solaris/unix system you can follow the steps in the video. Most likely you will need both sunstudio and gcc, as some code will not properly compile with the Sunstudio compiler. To build the best optimized binaries, I personally always try to use the SunStudio compiler and linker. Enough of the boring details, on with building a 64-bit version of rsync. Happy compiling ...
Tuesday, July 27, 2010
Tuesday, June 8, 2010
EON 0.60 ZFS binary kit snv_130 released!
Here it is finally, the long awaited EON 0.60 binary kit release based on snv_130 and other GNU compiled binaries. Hopefully, it was well worth the wait. I tried to complete all the requests for various packages but was unable to integrate them all cleanly (sabnzbd + dependency python) in this release. I will try to get the missed ones at a later time. It is uploaded in 5 parts. You can download bin-130a[a-e] manually and transfer all 5 files to your EON storage for installation or follow the steps below, which assumes you are using wget from an prior installed binary kit 124. So let's retrieve the files. These steps also assume your EON storage can reach the web.
Binary Kit 130 summary:
cd /tmp wget -O binkit-130.tgz http://i.minus.com/1323745623/7Aw7618NGr6qYvgEXEpkWw/dZLxUEf3SOTLh.tgzIf this is the first time using a binary kit, you will need to perform this step. If you have used previous binary kits, you can skip to the next step.
cd /zpool mkdir localThis step installs the new binary kit to /usr/local which is linked to /zpool_name/local.
cd /usr/local gzip -dc /tmp/binkit-130.tgz | tar -xf -This completes the binary kit install and typing "aria2c -v" should confirm if it worked. Below is a screenshot listing some of the binaries included:
Binary Kit 130 summary:
- PHP/libphp 5.3.1 (GD, jpeg, png support)
- Aria2c 1.9.3 (HTTP/HTTPS, FTP, BitTorrent and Metalink)
- tmux 1.1 (terminal multiplexer)
- screen (terminal multiplexer)
- wget/curl (retrieving files using HTTP, HTTPS and FTP)
- glusterfs 3.0 (clustered storage solution)
- stunnel (encrypt TCP connections inside SSL)
- socat (multi-purpose relay)
- bonnie/iperf (disk / network benchmarking)
- nano (editor)
- elinks (text browser)
- ddclient/inadyn (dynamic DNS clients)
- par2 (parity archive volume set)
cd /usr/local/bin ln -s ./i86/powertop .For 64 bit EON version:
cd /usr/local/bin ln -s ./amd64/powertop .
Wednesday, May 5, 2010
EON on a ZFS mirrored boot/root?
A typical operating system requires a boot disk and certain storage requirements to reside, boot and do what it's designed to do. The OS or boot disk where the operating system resides in a conventional install becomes a possible point of failure. The OS disk failing, would cause an outage and cut-off access to your data and storage appliance. RAID 1 or mirroring of the OS disk is often used to address/counter this type of failure. ZFS has the features to make an OS disk redundant by mirror-ing (RAID 1), providing an added layer of insurance to your storage appliance's uptime.
A design decision with EON, was to make it run from a RAM disk, hence it would not have an associated failure attached to the media(USB, CF or hard disk) it boots from or resides on. Size becomes a disadvantage running from a RAM disk but the trade off is an add layer of insurance, resilience and uptime. EON uses the boot/residence media mostly for out of band task that are not tied to performance and are not frequently used, so the typical 5+ MB/s performance of a USB/CF media is not a problem. After EON is booted, the USB media could be pulled (simulating a boot disk failure) and only the services below would be impacted. The important thing to note is that EON would continue to run, along with all the services enabled. The show goes on and facilitates dynamic repair or correction of the disk failure situation. EON uses the USB/CF media to preserve:
A design decision with EON, was to make it run from a RAM disk, hence it would not have an associated failure attached to the media(USB, CF or hard disk) it boots from or resides on. Size becomes a disadvantage running from a RAM disk but the trade off is an add layer of insurance, resilience and uptime. EON uses the boot/residence media mostly for out of band task that are not tied to performance and are not frequently used, so the typical 5+ MB/s performance of a USB/CF media is not a problem. After EON is booted, the USB media could be pulled (simulating a boot disk failure) and only the services below would be impacted. The important thing to note is that EON would continue to run, along with all the services enabled. The show goes on and facilitates dynamic repair or correction of the disk failure situation. EON uses the USB/CF media to preserve:
- edits to the configuration files
- edits to the grub menu entries or updating the image
- updates to the zpool.cache
- user optional binaries on the USB/CF media
Monday, April 5, 2010
EON ZFS Storage 0.60.0 based on snv 130, Sun-set release!
Embedded Operating system/Networking (EON), RAM based live ZFS NAS appliance is released on Genunix! This release marks the end of SXCE releases and Sun Microsystems as we know it! It is dubbed the Sun-set release! Many thanks to Al at Genunix.org for download hosting and serving the Opensolaris community.
New to EON, start here! Upgrading, see how to use transporter.sh
EON Deduplication ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:
EON 64-bit x86 CIFS ISO image version 0.60.0 based on snv_130
EON 64-bit x86 Samba ISO image version 0.60.0 based on snv_130
EON 32-bit x86 CIFS ISO image version 0.60.0 based on snv_130
EON 32-bit x86 Samba ISO image version 0.60.0 based on snv_130
EON 64-bit x86 CIFS ISO image version 0.60.0 based on snv_130 (NO HTTPD)
EON 64-bit x86 Samba ISO image version 0.60.0 based on snv_130 (NO HTTPD)
New/Changes/Fixes:
- Active Directory integration problem resolved
- Hotplug errors at boot are being worked on and are safe to ignore.
- Updated /mnt/eon0/.exec with new service configuration additions (light, nginx, afpd, and more ...).
- Updated ZFS, NFS v3 performance tuning in /etc/system
- Added megasys driver.
- EON rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
New to EON, start here! Upgrading, see how to use transporter.sh
EON Deduplication ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:
EON 64-bit x86 CIFS ISO image version 0.60.0 based on snv_130
- eon-0.600-130-64-cifs.iso
- MD5: 55c5837985f282f9272f5275163f7d7b
- Size: ~93Mb
- Released: Monday 05-April-2010
EON 64-bit x86 Samba ISO image version 0.60.0 based on snv_130
- eon-0.600-130-64-smb.iso
- MD5: bf095f2187c29fb543285b72266c0295
- Size: ~106Mb
- Released: Monday 05-April-2010
EON 32-bit x86 CIFS ISO image version 0.60.0 based on snv_130
- eon-0.600-130-32-cifs.iso
- MD5: e2b312feefbfb14792c0d190e7ff69cf
- Size: ~59Mb
- Released: Monday 05-April-2010
EON 32-bit x86 Samba ISO image version 0.60.0 based on snv_130
- eon-0.600-130-32-smb.iso
- MD5: bcf6dc76bc9a22cff1431da20a5c56e2
- Size: ~73Mb
- Released: Monday 05-April-2010
EON 64-bit x86 CIFS ISO image version 0.60.0 based on snv_130 (NO HTTPD)
- eon-0.600-130-64-cifs-min.iso
- MD5: f5922c98888521e4d8bef10133ccbe40
- Size: ~87Mb
- Released: Monday 05-April-2010
EON 64-bit x86 Samba ISO image version 0.60.0 based on snv_130 (NO HTTPD)
- eon-0.600-130-64-smb-min.iso
- MD5: e74732c41e4b3a9a06f52779bc9f8352
- Size: ~101Mb
- Released: Monday 05-April-2010
New/Changes/Fixes:
- Active Directory integration problem resolved
- Hotplug errors at boot are being worked on and are safe to ignore.
- Updated /mnt/eon0/.exec with new service configuration additions (light, nginx, afpd, and more ...).
- Updated ZFS, NFS v3 performance tuning in /etc/system
- Added megasys driver.
- EON rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
Saturday, March 6, 2010
What's the best pool to build with 3 or 4 disks?
I've been asked many times in variations, "I just started using EON and I'm new to opensolaris, What's the best pool to build with 3 or 4 disks"? I usually answer, it depends! Credit that reflex answer to Prof. Gordon, one of the best Calculus and Differential equations teacher that walked in my time. May the force be with you, wherever you are!
I'll use Richard Elling's research to explain. Let's say I have 500Gb drives, with IOPs (for avg, small, random, cache-miss, read I/O operations per sec) = 70.59 and max media bandwidth of 133Mbytes/s(includes read and write). What can we build?
With 4 disks in the first raidz set, we get higher bandwidth (399Mbytes/s) vs the 3 disk raidz bandwidth (266Mbytes/s), but the 3 disk raidz pool has a higher I/O operations per second capability. Note, as "sets" are added to the 3 disk raidz (3 disks each time) the difference of IOPS between the 4 disk raidz widens. If you exhaust the usable storage space, it will cost 4 or 3 times the cost of a drive for each new "Set", to add or grow the storage. So the 3 drive raidz has a more economical cost per set. This can be repeated to add more "Sets" or more storage and bandwidth as needed. So this is a very flexible choice. The change with 1 additional set would look like.
STRIPE
Has great bandwidth numbers, usable storage and IOPS, but any disk failure would cause the pool to fail and lose ALL your data. Did I mention that good storage is NOT a substitute for a GOOD backup? This pool is not easily expanded when the usable storage is exhausted and offers no data redundancy.
MIRROR
Has great bandwidth numbers, a higher cost per usable storage and allows failure of 2 disks. It has roughly twice the write bandwidth and up to 4 times the read performance as ZFS is capable of reading from all disks in the mirror in parallel. This configuration will most likely provide the best balance of performance and data protection at the expense of disks or usable storage. Expanding or growing this pool when the usable storage is being exhausted, is also simple.
Hopefully this will help architect pools that suits your workload, cost dynamics and growth needs.
I'll use Richard Elling's research to explain. Let's say I have 500Gb drives, with IOPs (for avg, small, random, cache-miss, read I/O operations per sec) = 70.59 and max media bandwidth of 133Mbytes/s(includes read and write). What can we build?
RAID Type Disks Sets Storage Space Performance (IOPS) Max BW(Mbytes/s) RAIDZ 4 1 3x500=1500Gb 4x70.59/3=94 3x133=399 RAIDZ 3 1 2x500=1000Gb 3x70.59/2=106 2x133=266 (1 spare) STRIPE 4 1 4x500=2000Gb 4x70.59=282 4x133=532 STRIPE 3 1 3x500=1500Gb 3x70.59=212 3x133=399 MIRROR 2 2 2x500=1000Gb 4x70.59=282 4x133=532RAIDZ
With 4 disks in the first raidz set, we get higher bandwidth (399Mbytes/s) vs the 3 disk raidz bandwidth (266Mbytes/s), but the 3 disk raidz pool has a higher I/O operations per second capability. Note, as "sets" are added to the 3 disk raidz (3 disks each time) the difference of IOPS between the 4 disk raidz widens. If you exhaust the usable storage space, it will cost 4 or 3 times the cost of a drive for each new "Set", to add or grow the storage. So the 3 drive raidz has a more economical cost per set. This can be repeated to add more "Sets" or more storage and bandwidth as needed. So this is a very flexible choice. The change with 1 additional set would look like.
RAID Type Disks Sets Storage Space Performance (IOPS) Max BW(Mbytes/s) RAIDZ 4 2 3000Gb 188 798 RAIDZ 3 2 2000Gb 212 532Both 4 and 3 disk raidz allows only 1 disk to fail but if all disks had the same probability of failure then the 4 disk raidz pool would have a higher probability of a failure than the 3 disk version.
STRIPE
Has great bandwidth numbers, usable storage and IOPS, but any disk failure would cause the pool to fail and lose ALL your data. Did I mention that good storage is NOT a substitute for a GOOD backup? This pool is not easily expanded when the usable storage is exhausted and offers no data redundancy.
MIRROR
Has great bandwidth numbers, a higher cost per usable storage and allows failure of 2 disks. It has roughly twice the write bandwidth and up to 4 times the read performance as ZFS is capable of reading from all disks in the mirror in parallel. This configuration will most likely provide the best balance of performance and data protection at the expense of disks or usable storage. Expanding or growing this pool when the usable storage is being exhausted, is also simple.
Hopefully this will help architect pools that suits your workload, cost dynamics and growth needs.
Wednesday, February 17, 2010
Traffic (QoS) control built into your EON ZFS storage
Your EON ZFS storage provides access to a lot of services, such as HTTP, HTTPS, SFTP, Firefly/daapd, AFP(AppleShare) and more. All of these services are available as a network resource. Wouldn't it be nice to be able to control or manage how different systems use these network resources, such as bandwidth?
Project Crossbow provides the controls to manage and virtual-ize network resources. The traffic controls (QoS) can be used to manage by transport (TCP, UDP, SCTP, iSCSI, etc), bandwidth limits, IP address and more.
For example, one could simply limit the amount of bandwidth the HTTP, HTTPS or SSH service can utilize. You could create virtual nics bound to your real interface and provide different levels of service and bandwith to these virtual or real nics. It allows for a very flexible storage setup where you can really manage the traffic and quality of service it delivers.
Let's do a simple 10Mbps bandwidth limit for HTTP via interface bge0 for a flow we will label httpflow. First, we create a flow that matches the HTTP service
Project Crossbow provides the controls to manage and virtual-ize network resources. The traffic controls (QoS) can be used to manage by transport (TCP, UDP, SCTP, iSCSI, etc), bandwidth limits, IP address and more.
For example, one could simply limit the amount of bandwidth the HTTP, HTTPS or SSH service can utilize. You could create virtual nics bound to your real interface and provide different levels of service and bandwith to these virtual or real nics. It allows for a very flexible storage setup where you can really manage the traffic and quality of service it delivers.
Let's do a simple 10Mbps bandwidth limit for HTTP via interface bge0 for a flow we will label httpflow. First, we create a flow that matches the HTTP service
flowadm add-flow -l bge0 -a transport=tcp,local_port=80 httpflowLet's view it
flowadm show-flowFinally, let's set bandwidth limits
flowadm set-flowprop -p maxbw=10m httpflowTo verify the properties
flowadm show-flowpropTo show traffic usage
flowadm show-usageAccounting can also be setup to record the usage. Rather than rehash the numerous possibilities, here are 2 links that details this feature fairly well. The first is written by Ben Rockwood and the other can be found here. Traffic control ... out!
Monday, February 1, 2010
Creating a EON ZFS storage self signed certificate
Your EON ZFS storage is available with 3 web server options, apache2(default), lighttpd, and nginx. They are provided with a self signed certificate that I created to simplify configuration and ease getting them started. The proper thing to do is replace it with your own certificate or create a self signed replacement.
Prerequisite(s): This requires the binary kit or an alternate system with a working openssl, to create your own self signed certificate.
The "\" means the command is one continuous line to create the self signed certificate. Feel free to experiment and substitute your own arguments for:
days = set to 365 x 10 = 3650 or ~10 yrs
CN = $HOSTNAME = replace with your own storage hostname
O = Gibraltar Engineering
OU = EON Secure Certificate
Prerequisite(s): This requires the binary kit or an alternate system with a working openssl, to create your own self signed certificate.
The "\" means the command is one continuous line to create the self signed certificate. Feel free to experiment and substitute your own arguments for:
days = set to 365 x 10 = 3650 or ~10 yrs
CN = $HOSTNAME = replace with your own storage hostname
O = Gibraltar Engineering
OU = EON Secure Certificate
openssl req -x509 -nodes -days 3650 -newkey rsa:1024 -keyout cert.key -out cert.pem \ -subj "/C=US/ST=NY/CN=$HOSTNAME/O=Gibraltar Engineering/OU=EON Secure Certificate"This will produce 2 files cert.key and cert.pem. For Apache2 they are configured and the proper permissions set as follows:
cp cert.pem /etc/apache2/2.2/server.crt cp cert.key /etc/apache2/2.2/server.key chmod 400 /etc/apache2/2.2/server.crt chmod 400 /etc/apache2/2.2/server.keyFor lighttpd the pem and key file are concatenated to create a single file
cp cert.pem /your_pool/lighttpd/etc cat cert.key >> /your_pool/lighttpd/etc/cert.pem chmod 400 /your_pool/lighttpd/etc/cert.pemFor nginx
cp cert.pem /your_pool/nginx/conf cp cert.key /your_pool/nginx/conf chmod 400 /your_pool/nginx/conf/cert.pem chmod 400 /your_pool/nginx/conf/cert.key
Wednesday, January 27, 2010
The SUN has set, for the last time!
On January 27th at approximately 9:50am, Oracle completed it's acquisition of Sun Microsystems for 7.4 billion all cash. The price is quite a steal considering Sun's history of innovations. It is also personally quite sad to see one of the greatest engineering companies in my lifetime, like a beautiful descending Sun-set, descend beyond the horizon.
I was introduced to SunOS over 15 years ago when I had to take an electrical engineering class (Feedback Control Systems) that required running simulations on MatLab. They were the early days of the world wide web and the beginning of an engineering love/career. My internships, from there on were Sun and Solaris related. One beautiful summer, I went to The Herff College of Engineering in Memphis to learn and port a Cochlear model written in C by Dr. T Wilson, to Java. Without plans to do so, I made a career on something I learned and loved, as a sidebar tool. That tool was engineered by Sun Microsystems and for this I humbly say, THANKS for the great ride and memories, ... thanks to everyone who made Sun Microsystems what it became, is, was. It will be missed ...
I was introduced to SunOS over 15 years ago when I had to take an electrical engineering class (Feedback Control Systems) that required running simulations on MatLab. They were the early days of the world wide web and the beginning of an engineering love/career. My internships, from there on were Sun and Solaris related. One beautiful summer, I went to The Herff College of Engineering in Memphis to learn and port a Cochlear model written in C by Dr. T Wilson, to Java. Without plans to do so, I made a career on something I learned and loved, as a sidebar tool. That tool was engineered by Sun Microsystems and for this I humbly say, THANKS for the great ride and memories, ... thanks to everyone who made Sun Microsystems what it became, is, was. It will be missed ...
Friday, January 15, 2010
EON ZFS Storage min and nginx web server
In a previous post, lighttpd was used as a add in web server for the EON ZFS min storage (NO HTTPD) users. Another web server option for the ZFS storage (NO HTTPD) image is nginx. This post will show how to easily add HTTPD service using the nginx web server.
Prerequisite(s): A storage pool must be created and a binary kit must be installed. The binary kit is needed because it contains libpcre, a dynamic library needed by nginx.
Let's get started adding a nginx web server, to our ZFS min (NO HTTPD) storage image. First, get the pre-built nginx version 0.8.32 here. I have also included compilation notes under the nginx section in case you wish to compile and add other features on your own. Transfer the nginx-0,8.32,tgz file to the storage pool via CIFS share, sftp or USB. Here, I start with the file located in /tmp and a storage pool named abyss. Substitute your zpool name for abyss.
Prerequisite(s): A storage pool must be created and a binary kit must be installed. The binary kit is needed because it contains libpcre, a dynamic library needed by nginx.
Let's get started adding a nginx web server, to our ZFS min (NO HTTPD) storage image. First, get the pre-built nginx version 0.8.32 here. I have also included compilation notes under the nginx section in case you wish to compile and add other features on your own. Transfer the nginx-0,8.32,tgz file to the storage pool via CIFS share, sftp or USB. Here, I start with the file located in /tmp and a storage pool named abyss. Substitute your zpool name for abyss.
cd /abyss gzip -dc /tmp/nginx-0.8.32.tgz | tar -xf -Now let's add the automation entries to /mnt/eon0/.exec. Also, execute the commands to create the necessary symlinks. These entries align paths entered in nginx.conf
(cd /usr ; ln -s ../abyss/nginx .)At this stage, the nginx web server is ready to run, but feel free to customize the /abyss/nginx/conf/nginx.conf and generate your own /abyss/nginx/conf/cert.pem, /abyss/nginx/conf/cert.key file. OpenSSL (part of the binary kit which is a pre-requisite for this post) would be needed to generate your own self signed cert file (cert.pem, cert.key). To start and automate the web server, run and add the following to /mnt/eon0/.exec.
/usr/nginx/sbin/nginx -c /usr/nginx/conf/nginx.conf
Tuesday, January 5, 2010
EON ZFS Storage min and lighttpd web server
If you run one of the EON ZFS (NO HTTPD) storage images that do not include a web server this post will show how to easily add HTTPD service using the lighttpd or nginx web server.
Prerequisite(s): A storage pool must be created and a binary kit must be installed. The binary kit is needed because it contains libpcre, a dynamic library needed by lighttpd.
Let's get started adding a lighttpd web server, to our ZFS min (NO HTTPD) storage image. First, get the pre-built lighttpd version 1.4.25 here. I have also included compilation notes under the lighttpd section in case you wish to compile and add other features on your own. Transfer the lighttpd-1.4.25.tgz file to the storage pool via CIFS share, sftp or USB. Here, I start with the file located in /tmp and a storage pool named abyss. Substitute your zpool name for abyss.
Prerequisite(s): A storage pool must be created and a binary kit must be installed. The binary kit is needed because it contains libpcre, a dynamic library needed by lighttpd.
Let's get started adding a lighttpd web server, to our ZFS min (NO HTTPD) storage image. First, get the pre-built lighttpd version 1.4.25 here. I have also included compilation notes under the lighttpd section in case you wish to compile and add other features on your own. Transfer the lighttpd-1.4.25.tgz file to the storage pool via CIFS share, sftp or USB. Here, I start with the file located in /tmp and a storage pool named abyss. Substitute your zpool name for abyss.
cd /abyss gzip -dc /tmp/lighttpd-1.4.25.tgz | tar -xf -Now let's add the automation entries to /mnt/eon0/.exec. Also, execute the commands to create the necessary symlinks. These entries align paths entered in lighttpd.conf
(cd /usr ; ln -s ../abyss/lighttpd .) (cd /var ; ln -s ../abyss/lighttpd .)At this stage, the lighttpd web server is ready to run, but feel free to customize the /abyss/lighttpd/etc/lighttpd.conf and generate your own /abyss/lighttpd/etc/server.pem file. OpenSSL (part of the binary kit which is a pre-requisite for this post) would be needed to generate your own self signed cert file (server.pem). To start and automate the web server, run and add the following to /mnt/eon0/.exec.
/usr/lighttpd/sbin/lighttpd -f /usr/lighttpd/etc/lighttpd.conf
Monday, December 21, 2009
EON ZFS Storage 0.59.9 based on snv 129, Deduplication release!
Embedded Operating system/Networking (EON), RAM based live ZFS NAS appliance is released on Genunix! This is the first EON release with inline Deduplication features! Many thanks to Genunix.org for download hosting and serving the opensolaris community.
EON Deduplication ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:
EON 64-bit x86 CIFS ISO image version 0.59.9 based on snv_129
EON 64-bit x86 Samba ISO image version 0.59.9 based on snv_129
EON 32-bit x86 CIFS ISO image version 0.59.9 based on snv_129
EON 32-bit x86 Samba ISO image version 0.59.9 based on snv_129
EON 64-bit x86 CIFS ISO image version 0.59.9 based on snv_129 (NO HTTPD)
EON 64-bit x86 Samba ISO image version 0.59.9 based on snv_129 (NO HTTPD)
- Deduplication, Deduplication, Deduplication. (That only used 1x the amount of storage space)
- The hotplug errors at boot are being worked on. They are safe to ignore.
- Cleaned up minor entries in /mnt/eon0/.exec. Added "rsync --daemon" to start by default.
- EON rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
EON Deduplication ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:

- eon-0.599-129-64-cifs.iso
- MD5: 8e917a14dbf0c793ad2958bdf8feb24a
- Size: ~93Mb
- Released: Monday 21-December-2009

- eon-0.599-129-64-smb.iso
- MD5: 2c38a93036e4367e5cdf8a74605fcbaf
- Size: ~107Mb
- Released: Monday 21-December-2009

- eon-0.599-129-32-cifs.iso
- MD5: 0dcdd754b937f1d6515eba34b6ed2607
- Size: ~59Mb
- Released: Monday 21-December-2009

- eon-0.599-129-32-smb.iso
- MD5: c24008516eb4584a64d9239015559ba4
- Size: ~73Mb
- Released: Monday 21-December-2009

- eon-0.599-129-64-cifs-min.iso
- MD5: 78b0bb116c0e32a48c473ce1b94e604f
- Size: ~87Mb
- Released: Monday 21-December-2009

- eon-0.599-129-64-smb-min.iso
- MD5: 57d93eba9286c4bcc4c00c0154c684de
- Size: ~101Mb
- Released: Monday 21-December-2009
- Deduplication, Deduplication, Deduplication. (That only used 1x the amount of storage space)
- The hotplug errors at boot are being worked on. They are safe to ignore.
- Cleaned up minor entries in /mnt/eon0/.exec. Added "rsync --daemon" to start by default.
- EON rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
Thursday, December 3, 2009
EON ZFS Storage 0.59.5 based on snv 125 released!
Embedded Operating system/Networking (EON), RAM based live ZFS NAS appliance is released on Genunix! Many thanks to Al Hopper and Genunix.org for download hosting and serving the opensolaris community.
EON ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:
EON 64-bit x86 CIFS ISO image version 0.59.5 based on snv_125
EON 64-bit x86 Samba ISO image version 0.59.5 based on snv_125
EON 32-bit x86 CIFS ISO image version 0.59.5 based on snv_125
EON 32-bit x86 Samba ISO image version 0.59.5 based on snv_125
EON 64-bit x86 CIFS ISO image version 0.59.5 based on snv_125 (NO HTTPD)
EON 64-bit x86 Samba ISO image version 0.59.5 based on snv_125 (NO HTTPD)
- removed iscsitgd and replaced it with COMSTAR (iscsit, stmf, itadm)
- added SUNWhd to image vs being in the binary kit.
- added rsync to image vs being in the binary kit. Updated version of rsync supports IPv6.
- added nge, yge and yukonx drivers.
- added (/etc/inet/hosts, /etc/default/init) to /mnt/eon0/.backup (TIMEZONE and hostname change fix)
- fixed error entry /mnt/eon0/.exec. Changed "zpool -a" to "zpool import -a"
- eon rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
EON ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:

- eon-0.595-125-64-cifs.iso
- MD5: a21c0b6111803f95c29e421af96ee016
- Size: ~90Mb
- Released: Thursday 3-December-2009

- eon-0.595-125-64-smb.iso
- MD5: 4678298f0152439867d218987c3ec20e
- Size: ~103Mb
- Released: Thursday 3-December-2009

- eon-0.595-125-32-cifs.iso
- MD5: 4b76893c3363d46fad34bf7d0c23548c
- Size: ~57Mb
- Released: Thursday 3-December-2009

- eon-0.595-125-32-smb.iso
- MD5: f478a8ea9228f16dc1bd93adae03d200
- Size: ~70Mb
- Released: Thursday 3-December-2009

- eon-0.595-125-64-cifs-min.iso
- MD5: c7b9ec5c487302c1aa97363eb440fe00
- Size: ~85Mb
- Released: Thursday 3-December-2009

- eon-0.595-125-64-smb-min.iso
- MD5: a33f34506f05070ffc554de7beaafd4d
- Size: ~98Mb
- Released: Thursday 3-December-2009
- removed iscsitgd and replaced it with COMSTAR (iscsit, stmf, itadm)
- added SUNWhd to image vs being in the binary kit.
- added rsync to image vs being in the binary kit. Updated version of rsync supports IPv6.
- added nge, yge and yukonx drivers.
- added (/etc/inet/hosts, /etc/default/init) to /mnt/eon0/.backup (TIMEZONE and hostname change fix)
- fixed error entry /mnt/eon0/.exec. Changed "zpool -a" to "zpool import -a"
- eon rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
Friday, November 20, 2009
Using napp-it webadmin with your EON ZFS storage
Many have asked for a web interface to administer their EON ZFS storage. I started a FreeNAS interface port a while back but time and keeping pace with their development proved unsustainable. I shared it in the download section as Freon for someone with better PHP resources to complete. I also posted a webmin howto a while back. The webmin web user admin, lacks only a ZFS and a CIFS module. It contains a Samba module which may be easy for one of you Perl guru's out there to extend as a CIFS module.
Prerequisites: This exercise assumes the binary kit is installed, for unzip. Or unzip with winzip and drag the folder into a CIFS share onto the storage, then run the following within the napp-it directory to correct the proper unix carriage return:
Prerequisites: This exercise assumes the binary kit is installed, for unzip. Or unzip with winzip and drag the folder into a CIFS share onto the storage, then run the following within the napp-it directory to correct the proper unix carriage return:
find . -type f -print | xargs -I {} dos2unix -ascii {} {}Another option, written by Alka Guenther for nexenta, called napp-it was extended to work with EON. He has a running thread on opensolaris.org. Here are the steps I took to get it running on my ZFS storage after downloading napp-it v 0.210. I transferred it to /tmp/napp-it-0.210.zip. Then
cd /var/apache2/2.2/cgi-bin unzip -aa /tmp/napp-it-0.210.zip chown webservd:webservd napp-it cd napp-it chmod -R 755 ./*Next we vi/edit admin.pl and comment (line 42 in v 0.210) the following
use CGI::Carp qw (fatalsToBrowser);to
#use CGI::Carp qw (fatalsToBrowser);And that's pretty much it. We point the browser to http://EON_ZFS_IP/cgi-bin/napp-it/admin.pl and you should be greeted by a login with no password, which you can immediately change. It is very configurable and I really liked the console command feature. So give it a try and help improve it.
Friday, November 6, 2009
How is EON ZFS storage working for you?
For release 0.59.5 based on snv_125 I am thinking of adding 2 more images. A 64-bit CIFS and Samba version without any embedded web server. These images would be able add a web server based on lighttpd, if needed. I'd like to hear your thoughts on this? With the great news that ZFS de-duplication is complete, we can hope to see a SXCE release. Many thanks to Jeff Bonwick, Bill Moore, Mark Maybee, Matt Ahrens, Adam Leventhal, George Wilson, Robin Guo and all the engineers who made this happen.
I would also appreciate your feedback/review in format(pros:, cons:, and other thoughts:), to understand how EON ZFS storage is filling/failing your storage needs, thus far. I may not be able to address all needs but it would be great to understand how EON is working with you, whether it's good, bad or indifferent.
Update for future releases based on feedback:
- shift SUNWhd, S.M.A.R.T and rsync to the core image, instead of the binary kit.
- attempt to add more intel, broadcom nic drivers. (Note: not all drivers can be added because of image size contribution. Also I have no way of testing with certain hardware. There is a mechanism to add your own drivers)
- add 2 new 64-bit CIFS and Samba versions, with NO HTTP service. Will rely on external lighttpd, if HTTP service is needed.
- add COMSTAR, to replace iscsitgtd.
- documentation to help new to opensolaris, beginners and less technical audience. It would help greatly if you, the user would document or do write-ups, based on your experiences and challenges with EON. I could add the write-up to the wiki to help others. Proper credit will be given for your work.
I would also appreciate your feedback/review in format(pros:, cons:, and other thoughts:), to understand how EON ZFS storage is filling/failing your storage needs, thus far. I may not be able to address all needs but it would be great to understand how EON is working with you, whether it's good, bad or indifferent.
Update for future releases based on feedback:
- shift SUNWhd, S.M.A.R.T and rsync to the core image, instead of the binary kit.
- attempt to add more intel, broadcom nic drivers. (Note: not all drivers can be added because of image size contribution. Also I have no way of testing with certain hardware. There is a mechanism to add your own drivers)
- add 2 new 64-bit CIFS and Samba versions, with NO HTTP service. Will rely on external lighttpd, if HTTP service is needed.
- add COMSTAR, to replace iscsitgtd.
- documentation to help new to opensolaris, beginners and less technical audience. It would help greatly if you, the user would document or do write-ups, based on your experiences and challenges with EON. I could add the write-up to the wiki to help others. Proper credit will be given for your work.
Monday, October 19, 2009
EON ZFS Storage 0.59.4 based on snv_124 released!
Embedded Operating system/Networking (EON), RAM based live ZFS NAS appliance is released on Genunix! Many thanks to Genunix.org for download hosting and serving the opensolaris community.
EON ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:
EON 64-bit x86 CIFS ISO image version 0.59.4 based on snv_124
EON 64-bit x86 Samba ISO image version 0.59.4 based on snv_124
EON 32-bit x86 CIFS ISO image version 0.59.4 based on snv_124
EON 32-bit x86 Samba ISO image version 0.59.4 based on snv_124
- initialization of ntpd, nscd at boot time, moved to /mnt/eon0/.exec
- added /mnt/eon0/.disable for K99local stop for a cleaner shutdown
- added /mnt/eon0/.purge to allow removing drivers and binaries not needed by your image
- new version of install.sh. Fixes a bug for virtual disks, multiple runs and improved error checking of stages
- new transporter.sh CLI to automate upgrades, backups or downgrades to backed-up versions
- eon rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
EON ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:

- eon-0.594-124-64-cifs.iso
- MD5: 4bda930d1abc08666bf2f576b5dd006c
- Size: ~89Mb
- Released: Monday 19-October-2009

- eon-0.594-124-64-smb.iso
- MD5: 80af8b288194377f13706572f7b174b3
- Size: ~102Mb
- Released: Monday 19-October-2009

- eon-0.594-124-32-cifs.iso
- MD5: dcc6f8cb35719950a6d4320aa5925d22
- Size: ~56Mb
- Released: Monday 19-October-2009

- eon-0.594-124-32-smb.iso
- MD5: 3d6debd4595c1beb7ebbb68ca30b7391
- Size: ~69Mb
- Released: Monday 19-October-2009
- initialization of ntpd, nscd at boot time, moved to /mnt/eon0/.exec
- added /mnt/eon0/.disable for K99local stop for a cleaner shutdown
- added /mnt/eon0/.purge to allow removing drivers and binaries not needed by your image
- new version of install.sh. Fixes a bug for virtual disks, multiple runs and improved error checking of stages
- new transporter.sh CLI to automate upgrades, backups or downgrades to backed-up versions
- eon rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"
Subscribe to:
Posts (Atom)