** Changed in: debian
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285156
Title:
mdadm RAID10 arrays cannot be rebuilt, will not use available spare
drives
Uploaded to intrepid-proposed with 2.6.27-10.20:
https://lists.ubuntu.com/archives/intrepid-changes/2008-November/009508.html
Current version in intrepid-updates/-security is 2.6.27.16.20 and according to
its changelog:
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_2.6.27-16.44/
Yeah it works again - super great thanks to you guys :)
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Tags added: verification-done
** Tags removed: verification-needed
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Yep, looks like it works fine here, thanks for the fix guys.
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Accepted linux into intrepid-proposed, please test and give feedback
here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: linux (Ubuntu Intrepid)
Status: New => Fix Committed
Target: in
** Changed in: mdadm (Ubuntu Intrepid)
Status: New => Invalid
** Changed in: linux (Ubuntu Intrepid)
Target: None => intrepid-updates
** Changed in: linux (Ubuntu Jaunty)
Target: intrepid-updates => None
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare
Thanks Andy. I think I got confused from the bug posting where it listed
that kernel for jaunty, not intrepid. I assumed that meant it wouldn't
be released to intrepid, but I guess that's incorrect. Thanks for
clearing it up.
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare
On Tue, Nov 18, 2008 at 06:16:30PM -, Graeme Humphries wrote:
> Hrm, I thought this was going to get patched for Intrepid as well as
> jaunty?
According to the launchpad bug a fix for this problem was committed to
Intrepid. It should appear in the 2.6.27-9.18 release which is
currently in pro
Hrm, I thought this was going to get patched for Intrepid as well as
jaunty?
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
not a bug in mdadm
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
This bug was fixed in the package linux - 2.6.27-9.18
---
linux (2.6.27-9.18) jaunty; urgency=low
[ Amit Kucheria ]
* Add the armel architecture
[ Leann Ogasawara ]
* Reboot stalls after installing Intrepid from alternate on a Dell
Optiplex 330
- LP: #293372
[ St
** Changed in: linux
Status: Unknown => Fix Released
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Commited to Intrepid
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
intrepid.git;a=commitdiff;h=3ba60c8318a7cc415cb86df1b395705ae4fe3d9a
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
Target: None => intrepid-updates
--
mdadm RAID10 arrays cannot be rebuilt, wil
SRU justification:
Impact: Simple typo prevents added spare disks of RAID10 arrays not to
be synced after one drive failures.
Fix: Upstream commit (queued to -stable) to fix an if statement.
Testcase: (see above)
** Attachment added: "Patch from upstream"
http://launchpadlibrarian.net/1947
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
Status: New => In Progress
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received
Thanks for the upstream bug, David. It's nice to see the kernel devs
have already patched this issue, looks like it was a pretty simple
regression from 2.6.26.
Ubuntu kernel team: is it possible to get this patch into the Intrepid
2.6.27 kernel packages, since this is a potential data loss bug, an
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=11967
Importance: Unknown
Status: Unknown
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a me
Hi folks,
This'll be fixed in 2.6.28; I was experiencing the same issue and
submitted a bug. See http://bugzilla.kernel.org/show_bug.cgi?id=11967
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notificatio
There's no packages for 2.6.26 in the repos anymore, so I built myself
some kernel packages from the 2.6.26-5.17 sources, which is listed as
the most recent pre-2.6.27 source package in launchpad.
Rebooted, and my array is happily syncing, so it definitely seems to be
a problem with 2.6.27.
--
m
I experienced the same problem (kernel 2.6.27.4). Fortunately, I still
could boot kernel 2.6.26.3 - my raid10 is rebuilding.
--
mdadm RAID10 arrays cannot be rebuilt, will not use available spare drives
https://bugs.launchpad.net/bugs/285156
You received this bug notification because you are a me
As per suggestion on #ubuntu-server, I tried removing /dev/sdc3, "dd
if=/dev/zero of=/dev/sdc3 bs=1M", and then readding it to see if that
would kick off a sync, but it didn't make a difference.
Going to try replacing with a totally different hard drive here shortly,
just to verify that isn't the
The other note I was going to make is that, as per the observations
upstream, it looks like this is a problem more with 2.6.27 than with
mdadm, so I'm going to add that to this ticket as well. mdadm seems to
do the job of re-adding failed devices fine, it's just the kernel that
isn't syncing the ar
Oh, meant to attach my current md status, which shows the problem very
well:
md1 : active raid10 sdc3[3](S) sda3[0] sdb3[1]
113859584 blocks 512K chunks 2 near-copies [3/2] [UU_]
I've added a new drive, md knows it exists, md knows there's a drive
missing... but it doesn't sync. No amount o
I'm also experiencing this issue on intrepid/amd64, and it appears to
have been noticed upstream as well (Debian Bug #495580).
This is a pretty severe bug for anyone using RAID10, as it means that
arrays can't be rebuilt and recovered after a drive failure.
** Bug watch added: Debian Bug tracker
25 matches
Mail list logo
