[Bug 613872] [NEW] md raid5 set inaccessible after some time.

[Rudi Daemen]

Public bug reported:

Binary package hint: linux-image-2.6.32-24-generic-pae

I upgraded from Ubuntu 8.04LTS to 10.04LTS last weekend, the system has
been running fine untill today. For some reasons the webserver/mysql
server stopped responding and I checked the console and noticed it being
flooded by input/output errors. I managed to type dmesg and that was
filled with this information as well. By now all services that had a
reference to "/var/" (Which is mounted on /dev/md2, a raid5 set based on
4 disks) had stopped.

After typing reboot the system came back up normally and mdadm started a
resync of the raid5 set. No dataloss on the raid set detected. I
immediately checked all the logs under /var/log and noticed they all
stopped at the point the input/output errors started flooding the
console. The errors that flooded the console did not end up in the dmesg
logs probably because the /dev/md2 raidset was completely unavailable at
the moment this occurred. The problem seems similar to the one I
reported here: https://bugzilla.kernel.org/show_bug.cgi?id=11328#c48

This issue was NOT present under Ubuntu 8.04 with the 2.6.24 kernel, it
was present under Debian Lenny with the 2.6.26 kernel. And unfortunately
this bug seems to be present at the 2.6.32 kernel as well... The system
has been running for about a year on 8.04LTS without any issues.

System information:
- Via Epia LT15000AG (Via CenterHaul Esther CPU, CX700 chipset), 1GB RAM
- SiI3124 PCI-X sata controller
- 2x Via Rhine II onboard NIC (VT6102)
- 4x Samsung Spinpoint 160GB SATA hard drive connected to the SiI3124 controller.

These drives are configured as follows:
- /dev/md0 is a 4 disk RAID1 set containing the '/' filesystem.
- /dev/md1 is a 4 disk RAID5 set used as swap.
- /dev/md2 is a 4 disk RAID5 set used as the '/var/' filesystem.

The system is running Ubuntu 10.04 LTS configured for only LTS packages
and completely up to date (Except for the new kernel image that was
ready for download this morning).

I will attempt to create a photograph of the console if the error occurs
again. Only thing I can get out of the dmesg log is the know bug that
has been with the kernel since 2002 for the Via Rhine ethernet adapters.
I've added a USB drive to the system and set up two sessions, one to
tail the kernel log and one to tail dmesg. Both are dumping the output
to a 512MB flash drive, this should be enough to capture the events
preceding the issues.

It is OK to consider this bug report incomplete until I managed to
capture some logs. Attached lspci -vvv and dmesg output from the last
boot.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
md raid5 set inaccessible after some time.
https://bugs.launchpad.net/bugs/613872
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.