ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1

Joe Peterson joe at
Sat Jan 26 22:24:02 PST 2008

Jeremy Chadwick wrote:
>> If this is widespread, I think the chances re slim that it is a
>> hardware problem in every case.
> I'm in definite agreement here.  I think it might be worthwhile to note
> what hardware we're all using, in case there's something similar between
> our systems (chipset, disk vendor, etc.).
> My system is as follows; timeouts were reported during an rsync of data
> from the ZFS stripe (ad8+ad10) to a UFS2 filesystem on ad6.  System
> eventually panic'd after remaining deadlocked (while kernel messages
> about timeouts kept printing on the console for ad6 only) for 10-15
> minutes.
> *   MB: Supermicro PDSMI+  (Intel ICH7-based)
> *  CPU: Intel Core 2 Duo E6600
> *  RAM: Corsair CM2X1024-6400 DDR2, 2GB
> *  ad4: WD Caviar SE WD2000JD (boot/OS)
> *  ad6: Seagate Barracuda 7200.10 ST3500630AS
> *  ad8: WD Caviar SE16 WD5000AAKS (ZFS stripe)
> * ad10: WD Caviar SE16 WD5000AAKS (ZFS stripe)
> * All drives are hooked up to the ICH7.
> * SMART stats showed no problems on any of the drives before or after.
> * RELENG_7, i386, ULE scheduler.

Mine is as follows:

*   MB: Tyan Trinity S2099
*  CPU: Pentium 4, 2.4GHz
*  RAM: Crucial DDR, ECC, CL2.5, Unbuffered 2GB (1/2 PC2100, 1/2 PC2700)
*  ad0: Seagate ST3500630A 3.AAE (1 UFS2 boot, 1 ZFS pool)
*  ad1: Seagate ST3160812A 3.AAH (not used by FreeBSD)
* Intel ICH4 UDMA100 controller
* ATI Radeon RV280 9250
* Intel PRO/1000 NIC
* 7.0-RC1, i386, ULE scheduler


More information about the freebsd-stable mailing list