@Dustin -- it appears there is a whole bunch of change in this area to
allow the raids to be created on the fly. I suspect that this is
occuring becase mdadmin made the raid with all devices which then
failed, but did not clear it down before rebuilding it in degraded mode,
and as such a disk was
** Tags added: regression-potential
** Summary changed:
- kobject_add_internal failed for dev-sda1 with -EEXIST, don't try to register
things with the same name in the same directory
+ Degraded RAID boot fails: kobject_add_internal failed for dev-sda1 with
-EEXIST, don't try to register things
** Tags added: bug-watch
--
kobject_add_internal failed for dev-sda1 with -EEXIST, don't try to register
things with the same name in the same directory
https://bugs.launchpad.net/bugs/334994
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Screenshot attached.
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/23151208/Screenshot.png
** Tags added: regression
--
kobject_add_internal failed for dev-sda1 with -EEXIST, don't try to register
things with the same name in the same directory
Using the mainline builds, I have verified that this problem is not exhibited
by the 2.6.29rc1 or 2.6.29rc6 kernels, as installed from:
* http://kernel.ubuntu.com/~kernel-ppa/mainline/
Hopefully that's enough to help isolate the patch. I suspect it's in or
around the md driver.
If you can
