I tested this weekend:
- in 2.6.32-61-lucid mdadm still didnt work correctly
- in 2.6.35-rc1-lucid, the bug seems to be fixed (mdadm assembled correctly)
** Tags added: kernel-bug-exists-upstream-v2.6.32.61-lucid kernel-fixed-
upstream-v2.6.35-rc1
--
You received this bug notification because yo
Having a look on the source, I'm confirmed, that the assembling problem
is related to the change indicated as:
0cc3a8b md: Fix handling for devices from 2TB to 4TB in 0.90
metadata.
resp. to the following lines in drivers/md/md.c (Line 850ff):
--
850 rdev->sectors = rdev->sb_s
Now I found time to do it.
I could track down the problem starting between revs. 2.6.32-36.79
(good) and 2.6.32-37.80 (bad).
The log gives the following changes concerning drivers/md:
---
git log --oneline Ubuntu-2.6.32-36.79..Ubuntu-2.6.32-37.80 drivers/md
3fe9b03 md/raid5: abort any pending p
Hi Christopher,
I will try to do the bisection,
however it may take some time,
until I'm able to do it
as the server is productive
René
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247064
Title:
Public bug reported:
I operate a raid server consisting of two hardware RAID6 arrays (11 2 TB disks
each), which are combined in a MD-raid (Raid0).
When booting Kernel 2.6.32-33, the Raid is assembled correctly:
cat /proc/mdstat:
Personalities : [linear] [multipath] [raid0]
