Table of Contents
This section describes changes to the "deb" packages that make up the part of Coraid Linux that is housed in our APT coraid.com repository.
In the interest of brevity, some routine updates will not be listed here. If, for example the aoe driver is compiled for a new kernel, such a change would not be listed. A new coraid-kernel-headers package won't be listed unless the nature of the package has changed significantly, not just for updates to match coraid-kernel.
Wait for md devices to be ready for reading in md-start, used by the
cln-init startup script. This change helps avoid a race where mdadm
returns but the md device is not quite ready to be mounted.
This version contains a fix for a bug that can cause premature timeouts of I/O when some paths to an AoE target are not responding.
This version adds support for an /etc/aoe/ifs.conf file, the
contents of which can cause /etc/init.d/cln-init to use the
aoe_iflist module parameter when loading the aoe driver.
This version contains a workaround for a problem with modinfo, used
by aoe-version, where the presence of aoe in the current working
directory causes modinfo to fail.
Compared to 64, this aoe driver has improved network congestion handling and improved behavior in discovering and (if needed) avoiding the remote MAC addresses of AoE targets.
This kernel reverts the e1000 driver to being a built-in driver for two reasons: 1) a CLN20a will have its interfaces renumbered when the e1000 driver is a loadable kernel module, and 2) netconsole, which is built into the kernel, cannot use an Intel port when the e1000 driver is a loadable kernel module.
This kernel has the rtc (real-time clock) driver built into the
kernel, because the debian startup scripts call "hwclock" to set the
system time before loading the modules in /etc/modules.
The relayfs module is also available in this kernel.
Version 64 of the aoe driver includes a more traditional congestion control algorithm that helps avoid AoE congestion when there is an imbalance between the number of local and remote ports.
This kernel contains bugfixes from the long-term stable 2.6.16.y branch as well as a backported XFS bugfix from Dave Chinner. (It is commit 20f4ebf2 in Linus Torvalds's git tree and SGI-PV: 959978.)
It also updates the e1000 driver to accept MTU settings only up to 8192 for the onboard Intel 82573 ports of the CLN 21. This e1000 driver, backported from 2.6.18.8, allows higher MTU settings that can cause the 82573 to drop packets. A good MTU (configured in /etc/aoe/mtu.conf) for eth2 and eth3 on a CLN21 is 4200.
Also the e1000 driver is a loadable kernel module.
The upstream udev package is no longer compatible with the long-term stable kernel used by the coraid-kernel package. This release of coraid-aptcfg pins the udev version at 114.
The testing branch, lenny, has changed so quickly and so fast that compatibility issues with the long-life stable 2.6.16.y kernel in coraid-kernel have begun to manifest.
The lenny release is about to go stable. Rather than following the next testing release, this update to coraid-aptcfg includes an /etc/apt/sources.list file that causes Coraid Linux to track lenny.
The unused and undocumented coraid-upgrade script is being removed to save confusion when CLN admins want to use the coraid-update script, a new relatively script that allows for a safer transfer of update files to Coraid storage appliances.
The location of the Coraid Linux APT repository has changed. The URI is nearly the same, with "support" replacing "www".
APT's default behavior has changed so that it installs packages that are listed in the "Suggests" and "Recommends" lines for a requested package.
An example of the result is that when attempting to upgrade from openssh-client from version 1:4.7p1-2 to version 1:4.7p1-9 with "apt-get install openssh-client", apt-get tries to install a large number of X11 packages.
This new coraid-aptcfg adds lines to the apt.conf file that maintain the old behavior, where only dependencies are treated as such.
Now that the amd64 architecture testing distribution is supported by the security updates APT repository, we can use it in /etc/apt/sources.list.
Using this new coraid-aptcfg, syslog-ng users can update their syslog-ng packages.
This update uses 4200 as the MTU for the onboard ethernet interfaces instead of 9000. These interfaces perform better with the 4 KiB payload.
It also makes sure that an "apt" directory exists in the tmpfs-backed /var/log filesystem.
The aoetools version 20 contains improvements over version 15 including support for new features in recent aoe drivers and a new "aoecfg" tool, which can perform the entire set of config query commands supported by the AoE protocol.
This release contains minor bugfixes and a new aoe_maxout module parameter, which can specify the maximum number of outstanding packets per AoE target to which no response has yet been received.
This kernel includes an e1000 driver backported from 2.6.18.8, which supports the Intel 82573V and 82573L chipsets.
In md-start, increase speed_limit_max and speed_limit_min in /proc
so that md initialization completes more quickly.
In cln-init, bring up all ethernet interfaces, not just eth1.
The Coraid Linux /etc/init.d/cln-init boot script now allows the MTU
setting to be overridden for a given interface in the
/etc/aoe/mtu.conf file.
The default MTU (for network interfaces that support it) is 9000. The override will be helpful when a network interface is capable of the default MTU but it is connected to a switch or host that does not support a 9000 MTU.
The aoetools-15 includes the new aoe-flush command, which asks the kernel to forget about AoE devices that are no longer up, or optionally to forget about all AoE devices that are not in use.
This version adds support for building the openafs module found in the openafs-modules-source package, in addition to the pre-existing support for the standalone aoe6 driver and the drbd0.7-module-source package.
In 2.6.16.40 there was an important RAID 1 fix that is included in this coraid-kernel release. Two other related packages were also released:
coraid-aoe - version 46-2.6.16.45-c1-1 coraid-kernel-headers - 2.6.16.45-c1-1
This release of aoe6-46 includes bugfixes and adds the ability to remove unused AoE devices from the kernel's list of block devices (with aoe-flush). This feature can help to avoid, for example, the long delay incurred when LVM times out in its attempt to read from long-gone AoE devices.
Now the cln-init script attempts to increase the MTU of all ethernet interfaces to 9000 when the CLN boots.
This headers package contains the kernel headers from the 2.6.16.35
kernel in the coraid-kernel package. It can be used to build custom
drivers for the CLN kernel.
Version 40 includes several
changes since
aoe6-32, including two somewhat obscure bugfixes and aoe-flush for helping
the aoe driver to forget about absent devices.
Release
version
12 of aoetools, which most notably includes aoe-flush.
This section describes changes that affect the base image that we ship on new CLNs. Readers will often be able to manually recreate the changes on their own CLNs.
Changes that appear in the Software Package Changes section will not be repeated here. Critical changes in debian packages may be listed here.
In order to save wear on the flash disk, the coraid-nolocate package modified the daily cron job that updated the updatedb for the "locate" command. The current CLN image contains no locate command and no such cron job.
Vulnerability CVE-2008-0166 is fixed in the openssl version 0.9.8g-10.
We have been in touch with the LVM developers, and the shortcomings that necessitated the creation of coraid-lvm2 appear to have been addressed, so Coraid Linux can use the lvm2 package from debian testing now.
There is no longer a need to use the samba from stable, since testing has a version that includes fixes for CVE-2007-2444, CVE-2007-2446, and CVE-2007-2447.
LVM commands called from heartbeat scripts were having trouble
finding the libraries under /opt/lib. By putting that directory in
/etc/ld.so.conf and running ldconfig on the CLN master, this
problem should be avoided.
To address three security problems, security updates from debian stable were used in the CLN image.
CLN admins can install these packages themselves using dpkg.
makki:~# cd /tmp makki:/tmp# wget -q http://security.debian.org/debian-security/pool/updates/main/s/samba/samba_3.0.24-6etch1_amd64.deb makki:/tmp# md5sum samba_3.0.24-6etch1_amd64.deb 0f3a2fdcb3f6eb6fc389b3e59e8f5322 samba_3.0.24-6etch1_amd64.deb makki:/tmp# wget -q http://security.debian.org/debian-security/pool/updates/main/s/samba/samba-common_3.0.24-6etch1_amd64.deb makki:/tmp# md5sum samba-common_3.0.24-6etch1_amd64.deb 117b0b1a3193555a92616ee3ff0da86e samba-common_3.0.24-6etch1_amd64.deb makki:/tmp# dpkg -i samba*.deb
These fixes should be included in the next release of the testing samba packages.
It is used in testing during production, only takes up 168 KB, and is often installed by customers anyway, so ethtool is becoming part of the base CLN image.
This release fixes the "remotely controllable function pointer" bug, CVE-2006-6235.
On performing the apt-get update command, a warning was generated.
W: There are no public key available for the following key IDs: A70DAF536070D3A1
After updating the debian keyring with the command below, the missing key is added to the system.
apt-get install debian-archive-keyring