Wouldn't #358054 be somehow related?
--
Degraded RAID boot fails: 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
https://bugs.launchpad.net/ubuntu/+bug/358054
--
Degraded RAID boot fails: 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
** Changed in: linux (Ubuntu Jaunty)
Status: In Progress = Fix Committed
--
Degraded RAID boot fails: 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
This bug was fixed in the package linux - 2.6.28-11.40
---
linux (2.6.28-11.40) jaunty; urgency=low
[ Amit Kucheria ]
* Disable DEVKMEM for all archs on Jaunty
- LP: #354221
[ Andy Whitcroft ]
* SAUCE: md: wait for possible pending deletes after stopping an array
-
@Dustin -- thanks for your testing, I could no longer reproduce the
issue locally either with this patch in place. Will push it to the
kernel-team.
--
Degraded RAID boot fails: kobject_add_internal failed for dev-sda1 with
-EEXIST, don't try to register things with the same name in the same
I'm marking this invalid against mdadm. I have tried a variety of fixes
from upstream source related to incremental md assembly, merged both
2.6.8 and 2.6.7.2 from Debian into Jaunty, and none of these solve the
issue.
Meanwhile, Andy has confirmed that he can see the race condition in the
Added some debugging to the teardown code and managed to reproduce this.
What we find is that we unbind and then attempt and fail a bind on the
array, then we see the deletes for the unbind complete. This leads to
the bind failure:
[3.476504] md: bindsda1
[...]
[ 35.097882] md:
I tested Andy's test kernels on my host, with my host cpu in each of the
following configurations:
Pinned
* 2.4GHz
* 2.0GHz
* 1.6GHz
* 1.2GHz
* 800MHz
Dynamic
* Conservative
* Ondemand
* Performance
* Powersave
I could no longer reproduce the issue, it appears to be fixed! Big
** Changed in: linux (Ubuntu Jaunty)
Target: ubuntu-9.04-beta = ubuntu-9.04
--
Degraded RAID boot fails: 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
Ok, I have managed to reproduce this in a KVM here. Console output is
as below, dmesg output attached:
** WARNING: There appears to be one or more degraded RAID devices **
The system may have suffered a hardware fault, such as a disk drive
failure. The root device may depend on the RAID
I should also note that the kernel is not lying, these file are visibly
present in sysfs:
(initramfs) ls /sys/devices/virtual/block/md0/md
dev-sda1 safe_mode_delay resync_start raid_disks
reshape_position new_dev component_sizelayout
array_state
** Changed in: linux (Ubuntu Jaunty)
Status: Confirmed = In Progress
--
Degraded RAID boot fails: 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
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jaunty)
Status: In Progress = Invalid
--
Degraded RAID boot fails: kobject_add_internal failed for dev-sda1 with
-EEXIST, don't try to register things with the same name in the same
ok i have been unable to reproduce with the images I have. however it
seems that the issue is a userspace interaction and is fixed in the
debian mdadm. we need to sync that into ubuntu. the kernel task is now
closed, and this targetted against mdadm.
** Changed in: mdadm (Ubuntu Jaunty)
** Changed in: mdadm (Ubuntu Jaunty)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
Status: New = Triaged
--
Degraded RAID boot fails: kobject_add_internal failed for dev-sda1 with
-EEXIST, don't try to register things with the same name in the same directory
Actually, I have to re-open the kernel task.
This is a problem exhibited by the Ubuntu 2.6.28 kernel, which is not
present in 2.6.29. We can hack our way around this perhaps with an
updated userspace mdadm package, but the error message in this bug's
description still appears, and we get kernel
After some testing done a system with a RAID1 array here are my results:
mdadm 2.6.7.2: unable to boot from a degraded RAID1 array.
mdadm 2.6.8: able to boot from a degraded RAID1 array.
- jaunty kernel 2.6.28-11-server: error messages are printed on the console
(as shown in the attached
** Changed in: linux (Ubuntu)
Target: jaunty-alpha-6 = ubuntu-9.04-beta
--
Degraded RAID boot fails: 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
On Tue, Mar 10, 2009 at 12:39:35PM -, Dustin Kirkland wrote:
Are you thinking this is a kernel or userspace problem, Andy?
I do not know for sure right now. I would say that the kernel thinks it
is doing something sensible. That the array is already present in some
sense and it is
** Tags removed: bug-watch
--
Degraded RAID boot fails: 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,
Are you thinking this is a kernel or userspace problem, Andy?
:-Dustin
--
Degraded RAID boot fails: 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
21 matches
Mail list logo
