[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#406915: marked as done (access to large RAID arrays on Adaptec 2400A RAID controller with dpt_i2o module causes system hang)

Your message dated Sun, 3 Feb 2008 23:49:56 +0100
with message-id <20080203224956.GM4941@stro.at>
and subject line access to large RAID arrays on Adaptec 2400A RAID controller with dpt_i2o module causes system hang
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kernel-image-2.6.8-3-k7
Version: 2.6.8-16sarge6
Severity: critical
Justification: causes serious data loss


The system has built in an Adaptec 2400A RAID controller with two 80 GB
disks attached which are configured as RAID 1. The controller is handled
by the dpt_i2o module.

In this configuration everything works fine. (The RAID array is
exclusively used for data storage [samba server], the operating system
is installed on a separate single IDE disk which is attached to the
motherboard's IDE controller).

When I attach two 500 GB disks to the controller instead of the 80 GB
disks and configure them as RAID 1 array, the problems begin.
Partitioning the array with cfdisk works, building the file system with
mkfs.ext3 or mkreiserfs works, too. But copying data with cp to the
partition causes cp to hang after some time and some files were copied.
With an other console, changing to the directory in which the partition
on the array is mounted causes this console to hang, too. 'shutdown -h
now' (again in an other console) displays the shutdown-message, but the
system doesn't do a shutdown.

After a hard reset, it depends on the file system, whether there are
data on the array or not. With ext3 there are none of the copied files
on the array, with reiserfs there are the files on the array which were
copied before cp hung.

I tried to google for the problem and found a post on google groups
which seems to be related to the problem. The message-id is
<3XOno-5Pz-19@gated-at.bofh.it>

With the 2.4.27-2-386 kernel, everything seems to work, even with the
500 GB RAID array.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-k7
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages kernel-image-2.6.8-3-k7 depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  initrd-tools                  0.1.81.1   tools to create initrd image for p
ii  module-init-tools             3.2-pre1-2 tools for managing Linux kernel mo

-- no debconf information

--- End Message ---
--- Begin Message --- 
closing as upstream bugzilla has info that such situation happens with
consumer drive's error recovery sets up an interference pattern with the
RAID card's recovery

the bug has been marked as rejected as firmware issue from adaptec side.

--- End Message ---
Reply to: