I2O on Linux - Download
Kernel patches
Application patches
- raidutils_upstream_bugfixes.patch
Changes:
- use the proper data buffer on the I2OGETIOPS ioctl
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332229
- give explicit error messages instead of a misleading message
regarding "/dev/dpti17" when no control device files are found
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413136
- fix "raidutil -e" command to avoid leaking shared memory segments and leaving the spawned "raideng" process running indefinitely
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273577
- raidutils-0.0.6.tar.bz2
raidutils-0.0.6-1.i386.rpm
raidutils-0.0.6-1.src.rpm
Adaptec raidutils to manage the RAID-Controller. It also work with the dpt_i2o driver.
- grub-0.96-i2o.patch
To boot from an I2O controller, this patch has to be applied to grub. Without it, grub didn't recognize the block device.
- grub-0.94-i2o.patch
To boot from an I2O controller, this patch has to be applied to grub. Without it, grub didn't recognize the block device.
- lvm-i2o.patch
To create a PV on an I2O RAID array, you have to apply this patch to LVM2. Without it, the RAID array isn't recognized by LVM2.
Kernel patches
- i2o-config-clean.patch
Changes the formating of the header in i2o_config.c.
included in 2.6.7
- i2o-passthru.patch
Patch to get the raidutils work with the 2.6.x kernel. (Note: you need to apply the i2o-config-clean.patch before the i2o-passthru.patch works!). There was an error in the patch, which is now resolved (thanks to Fox).
included in 2.6.7
- i2o_cmd_passthru-reorder.patch
Changes ordering of the arguments in struct i2o_cmd_passthru.
included in 2.6.7
- i2o_config-checking-bugfix.patch
Patch to fix missing boundary checks in i2o-passthru.patch and return value of get_user (thanks to Jeff Garzik).
included in 2.6.7
- i2o_block-cleanup.patch
Patch to fix problems with i2o_block:
- more than 3 "visible" disks (hda, hdb, hdc, hdd) lead to kernel panics.
- removes some unused code with partitions.
- I2O_LOCK was often called with the addresses of the controller, and not with the address of the device. This wasn't discovered yet, because each device uses the same queue on the same controller, and there was only one controller.
- the cleanup function for gendisk (del_gendisk) doesn't work if the queue is shared between different devices. To workaround the queue is removed before.
- redundant code removed in module initialization and remove, use i2ob_new_device and i2ob_del_device instead.
- added all changes from Jens Axboe
included in 2.6.7
- i2o-64-bit-fix.patch
- provides i2o_context_list_*() functions, which maps 64-bit pointers to 32-bit context id's in a dynamic list. Note that you could use these functions on 32-bit and 64-bit systems, because on 32-bit systems the functions would be a static inline.
- i2o_scsi now uses the i2o_context_list_*() functions for transaction context.
included in 2.6.7
- i2o-makefile-cleanup.patch
Cleans up the configuration options and Makefile. Also now work on 64-bit systems.
included in 2.6.7
- i2o_proc-lct-access-bugfix.patch
Patch fixes problem in i2o_proc, which kernel panics when /proc/i2o/iopX/lct is accessed to the end.
included in 2.6.7
- i2o_proc-full-seq_file.patch
Patch converts all function, which not uses seq_file already to use it.
included in 2.6.7
- i2o-adaptec-zerochannel-support.patch
Patch includes support for ASR-2000S, ASR-2005S, ASR-2010S and ASR-2015S.
included in 2.6.8
- i2o-pae-support.patch
Include Adaptec specific PAE support.
WARNING: this patch is alpha! At the moment i2o_core and i2o_block should work, but because we have no hardware to test it, it is unknown, if it works at all. Most changes are taken from dpt_i2o.
- i2o-build_92.patch.bz2
Patch against 2.6.7 to get I2O subsystem build 92.
included in 2.6.9
- i2o-build_99.patch.bz2
Patch against 2.6.7 to get I2O subsystem build 99.
included in 2.6.9
- i2o-build_99-100.patch
Bugfix patch against 2.6.8-rc2-mm1.
included in 2.6.9
- i2o-build_100-103.patch
Another bugfix patch.
included in 2.6.9
- i2o-build_103-105.patch
Fixes devfs naming problems.
included in 2.6.9
- i2o-build_111.patch.bz2
Patch against 2.6.8 to get I2O subsystem build 111.
included in 2.6.9
- i2o-build_111-114.patch
Patch against build 111 to get I2O subsystem build 114. Mostly SCSI-OSM cleanup and bug fixing.
included in 2.6.9
- i2o-ioremap-limit.patch
Patch to lower the memory needed by the I2O controller for its queue.
included in 2.6.9
- i2o-increase_lct_get_timeout.patch
Patch to increase the timeout to wait for the LCT. On some systems the time to get a reply from the I2O controller was longer than the timeout.
included in 2.6.10
- i2o-2.6.11_1.288.patch.bz2
Patch to build 1.288 for 2.6.11 kernel.
- i2o_block-event-free-fix.patch
Patch to fix memory leak in I2O Block event handling.
- i2o_config-api-2.6.13-rc5-mm1.patch
Patch for new API for 2.6.13-rc5-mm1 kernel.
- i2o-bugfix-2.6.16.patch
Bugfix patch for 2.6.16 kernel.
included in 2.6.17
Subversion:
- Subversion web access for raidutils
Raidutils from Adaptec with the BSD-style license are available. You can access read-only with user "anonymous" and no password. To check out the latest version the first time enter:
svn co http://i2o.shadowconnect.com/svn/repos/raidutils/trunk
To update to the latest version, go to the directory and enter:
svn update
You must generate the configuration files by running the configuration script in the root directory:
./autogen.sh
- Subversion web access for kernel patches
You could also check out the latest patches and source files by entering:
svn co http://i2o.shadowconnect.com/svn/repos/kernel/trunk
THE SOFTWARE AND INFORMATION ON THIS SITE IS PROVIDED BY SHADOW CONNECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SHADOW CONNECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE OR INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Sponsored by 
last updated: 2008-02-09