[Bug 461673] New: xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0
xend ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 44, in <module> from xen.xend.server import SrvDaemon File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py",
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash+F@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c1 Summary: xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0 Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Blocker Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: pgnet.trash+F@gmail.com QAContact: qa@suse.de Found By: Customer i've been successfully running a headless install of OpenSuse 11.0 + Xen 321 as a Xen Dom0 w/ multiple DomUs for quite awhile ... i just built up a new OpenSuse 11.1 + Xen 331 box. short story -- Xen Dom0 on 11.1 w/ RAID-1 is not working; not clear as to why not. drop back to same setup on v11.0 -- all's ok. i've now reproduced this on another box, so posting it as a bug (?). i'm happy to provide any info -- just need some guidance as to where to look .. here are the 'gory details': i've partitioned, as always, as RAID-1 across two disks, sda + sdb, each part1 150 MB, LinuxRaid part2 10 GB, LinuxRaid part3 *, LinuxRaid RAID-1 /dev/md0 = sda1 + sdb1, mount_pt = '/boot', ext3 /dev/md1 = sda2 + sdb2 Volume Group "System" Logical Volume "Swap", mount_pt = 'swap', 512 MB, Logical Volume "Root", mount_pt = '/', * /dev/md2 = sda3 + sdb3 with this setup, boot to non-xen kernel works perfectly, as it did on OpenSuse 11.0, uname -a Linux server 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux lsb_release -r Release: 11.1 cat /etc/fstab /dev/md0 /boot ext3 acl,user_xattr 1 2 /dev/System/Root / ext3 acl,user_xattr 1 1 /dev/System/Swap swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 dmesg | egrep -i "fs|mount" Mount-cache hash table entries: 256 ACPI: Checking initramfs for custom DSDT Unpacking initramfs... done VFS: Disk quotas dquot_6.5.1 usbcore: registered new interface driver usbfs EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. df -H Filesystem Size Used Avail Use% Mounted on /dev/mapper/System-Root 13G 2.1G 9.8G 18% / udev 4.2G 160k 4.2G 1% /dev /dev/md0 152M 52M 92M 37% /boot next, i've installed zypper in -t pattern xen-server rpm -qa | grep -i xen kernel-xen-base-2.6.27.7-9.1 xen-libs-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 kernel-xen-2.6.27.7-9.1 kernel-xen-extra-2.6.27.7-9.1 xen-3.3.1_18494_03-1.8 on attempt to boot to xen kernel, it fails. @ boot console I see mention of '/var' not available scroll quickly by, and something about fsck.ext3 failing ... then i'm dumped @ a console prompt: "fsck failed for at lease one filesystem (not /). Please repair manually and reboot. The root file system is is already mounted read-write. Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work. Give root passwod for login:" I enter the password ... "if: Expression Syntax. (none) /root # (none) /root # ls -ald /var /boot drwxr-xr-x 15 root root 4096 Dec 19 18:20 /var drwxr-xr-x 2 root root 4096 Dec 19 18:12 /boot (none) /root # ls /boot (none) /root # > Is it that boot is not mounted? > try mount /boot (none) /root # (none) /root # mount /boot "EXT3-fs: unable to read superblock mount: wrong fs type, bad option, bad superblock on /dev/md0" (none) /root # (none) /root # reboot ... which, despite the admonition above, DOES work ... checking, nothing is written to /var/log/xen/xend.log or /var/log/messages. rebooting to non-xen kernel, all is ok again. at the non-xen kernel system's prompt, checking, service xend start returns simply xend unused and, line 26, in <module> import relocate File "/usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py", line 28, in <module> from xen.xend import XendDomain File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 35, in <module> from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 20, in <module> from xen.xend import balloon, sxp, image File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 44, in <module> xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)') It was pointed out to me elsewhere that, > xend can't start on a non-xen kernel, it doesn't have /proc/xen/* etc. If true, then, I've clearly misread this @ http://en.opensuse.org/Installing_Xen3: "... Next you can activate the Xen daemon: /etc/init.d/xend start insserv –d xend Finally you have to reboot your system: reboot ..." which seems to me to imply that 'xend' can be started before rebooting into the xen kernel ... for debugging, I'm in the process of trying to communicate with the box via serial port to capture the Xen startup process output. no luck with serial comms -- yet ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User wkong@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c1 wei kong <wkong@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wkong@novell.com --- Comment #1 from wei kong <wkong@novell.com> 2008-12-22 22:43:25 MST --- Boot xen kernel first. --thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash+F@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c3 --- Comment #3 from pgnet _ <pgnet.trash+F@gmail.com> 2008-12-23 19:00:21 MST --- (In reply to comment #1 from Wei Kong)
Boot xen kernel first.
You might read the post ... "on attempt to boot to xen kernel, it fails." -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash+F@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c4 --- Comment #4 from pgnet _ <pgnet.trash+F@gmail.com> 2008-12-23 19:01:37 MST --- i believe this has also been seen, now, my someone else ... http://forums.opensuse.org/install-boot-login/402759-opensuse-11-1-xen-sw-ra... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User wkong@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c5 --- Comment #5 from wei kong <wkong@novell.com> 2008-12-23 22:30:57 MST --- Ok, I can reproduce this bug. Now you can choose all xen packages when install os in "Software" to skip this bug. I will investigate this bug later. It seems that /etc/init.d/boot.md works incorrectly. --thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User xwhu@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c6 --- Comment #6 from Xinwei Hu <xwhu@novell.com> 2008-12-24 00:23:46 MST --- Created an attachment (id=262365) --> (https://bugzilla.novell.com/attachment.cgi?id=262365) patch to setup-md.sh patch to setup-md.sh -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User xwhu@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c7 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xwhu@novell.com --- Comment #7 from Xinwei Hu <xwhu@novell.com> 2008-12-24 00:29:43 MST --- The mdadm.conf in initrd contains duplicated entry for md0. This bug is not xen specific. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash+F@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c8 --- Comment #8 from pgnet _ <pgnet.trash+F@gmail.com> 2008-12-24 07:51:57 MST --- (In reply to comment #7 from Xin Wei Hu)
patch to setup-md.sh The mdadm.conf in initrd contains duplicated entry for md0.
I applied the patch as provided. @ reboot to kernel-xen, still fails as above. i'm dumped to the (none) /root # prompt, and, "/boot" is still empty ... i.e., md0 apparently not mounted correctly.
This bug is not xen specific.
just curious -- if that's the case, why does booting to non-xen kernel work? only the kernel-xen case fails. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c9 --- Comment #9 from pgnet _ <pgnet.trash@gmail.com> 2008-12-24 08:58:03 MST --- invoking the "not enough coffee" excuse ... applying the patch, then NOT forgetting to, mkinitrd -k "/boot/vmlinuz-xen" -i "/boot/initrd-xen" after reboot, i've now, uname -a Linux server 2.6.27.7-9-xen #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux and, df -H | grep boot /dev/md0 152M 52M 92M 37% /boot any other checks required/suggested to ensure all's well? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User stbinner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c10 Stephan Binner <stbinner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical --- Comment #10 from Stephan Binner <stbinner@novell.com> 2008-12-25 04:54:57 MST --- Please read http://en.opensuse.org/Bugs/Definitions -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c11 --- Comment #11 from pgnet _ <pgnet.trash@gmail.com> 2008-12-25 09:03:43 MST --- (In reply to comment #10 from Stephan Binner)
Please read http://en.opensuse.org/Bugs/Definitions
Other than for general information, do you have a particular point to make? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User xwhu@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c12 --- Comment #12 from Xinwei Hu <xwhu@novell.com> 2008-12-25 19:12:29 MST --- (In reply to comment #8 from pgnet _)
just curious -- if that's the case, why does booting to non-xen kernel work? only the kernel-xen case fails.
It'll fail if you run mkinitrd against non-xen kernel. (In reply to comment #9 from pgnet _)
any other checks required/suggested to ensure all's well?
I don't think there need to have other checks ;) Merry Xmas. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c13 --- Comment #13 from pgnet _ <pgnet.trash@gmail.com> 2008-12-25 20:32:28 MST --- (In reply to comment #12 from Xinwei Hu)
I don't think there need to have other checks ;)
Good enough. On to figuring out the next 'issue' with Xen ... :-)
Merry Xmas.
Likewise! Cheers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c14 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |xwhu@novell.com --- Comment #14 from Jan Beulich <jbeulich@novell.com> 2009-01-05 01:17:16 MST --- As I understand it this is not a kernel problem: Mind taking ownership of this? Otherwise, has the fix been pushed out? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User xwhu@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c15 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jbeulich@novell.com |xwhu@novell.com Status|NEEDINFO |ASSIGNED Info Provider|xwhu@novell.com | --- Comment #15 from Xinwei Hu <xwhu@novell.com> 2009-01-05 23:28:44 MST --- Sure. I'll take care of it then. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 pgnet _ <pgnet.trash@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mmarek@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mmarek@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|xwhu@novell.com |mmarek@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User dbt@genion.de added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c21 Tobias Kronwitter <dbt@genion.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |dbt@genion.de --- Comment #21 from Tobias Kronwitter <dbt@genion.de> 2009-02-04 15:19:12 MST --- Hello, I posted the following last december: http://forums.opensuse.org/install-boot-login/402759-opensuse-11-1-xen-sw-ra... Today I tried the mentioned solution and patched setup-md.sh an rebuild initrd-xen afterwards. However with no success: Now I do get the missing md-device (which schould be md0 (sda1, sdb1)) but as device md127. The mdadm.conf file looks like: DEVICE partitions ARRAY /dev/md0 level=raid1 UUID=081a1bd5:d2cfebd3:3d5369e9:2c7af0a6 ARRAY /dev/md1 level=raid1 UUID=6c203ec1:9360f8ba:da20cf36:64ef942c ARRAY /dev/md2 level=raid1 UUID=96498c7c:8cac6295:1f678b78:d723672a The unknown /dev/md127 device can of course not be mounted: /dev/md0 /boot ext3 acl,user_xattr 1 2 /dev/md1 swap swap defaults 0 0 /dev/root_dg/root_dg_vol00 / ext3 acl,user_xattr 1 1 Is there a solution yet ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c22 --- Comment #22 from pgnet _ <pgnet.trash@gmail.com> 2009-02-04 17:59:44 MST --- md seems to change/use device names (sdX) depending on what & how many drives are attahced; i haven't yet figured out the details. try mounting by UUID, rather than device. e.g., check what devices are in your /boot partition's RAID array, cat /proc/mdstat | grep md0 md0 : active raid1 sda1[0] sdb1[1] ^^^^ ^^^^ then, for those devices, find the correct ID, ls -al /dev/disk/by-id | egrep "sda|sdb" | grep ata | grep -v part lrwxrwxrwx 1 root root 9 2009-01-29 11:17 ata-ST###1 -> ../../sda lrwxrwxrwx 1 root root 9 2009-01-29 11:17 ata-ST###2 -> ../../sdb assuming, e.g., cat /etc/grub.conf setup (hd1) (hd1,0) setup (hd0) (hd0,0) use those IDs to mount by, cat /boot/grub/device.map (hd1) /dev/disk/by-id/ata-ST###2 (hd0) /dev/disk/by-id/ata-ST###1 finish up with, grub --batch < /etc/grub.conf using the above, with the patches applied, my mounts as in /etc/fstab /dev/md0 /boot ext3 acl,user_xattr 1 2 /dev/vg0/ROOT / ext3 acl,user_xattr 1 1 /dev/vgS/SWAP swap swap defaults 0 0 proc /proc proc defaults 0 0 ... work fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User dbt@genion.de added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c23 Tobias Kronwitter <dbt@genion.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P4 - Low --- Comment #23 from Tobias Kronwitter <dbt@genion.de> 2009-02-05 00:40:54 MST --- @ pgnet - mounting the devices "by-id" is an excellent idea - thank you. Sometimes you have to leave your old paths and habits and think innovative :-)) Assuming, that the UUID of the md-devices remain constant, and all the md devices find their physical devices by conventional device-path (true in my case) all I had to change, was the /etc/fstab: #/dev/md1 /boot ext3 acl,user_xattr 1 2 #/dev/md1 swap swap defaults 0 0 /dev/disk/by-id/md-uuid-081a1bd5:d2cfebd3:3d5369e9:2c7af0a6 /boot ext3 acl,user_xattr 1 2 /dev/disk/by-id/md-uuid-6c203ec1:9360f8ba:da20cf36:64ef942c swap swap defaults 0 0 /dev/root_dg/root_dg_vol00 / ext3 acl,user_xattr 1 1 The workaround works. The XEN-kernel (Dom0) is up and running !! :-)) The original md0-device (still present in non-xen kernel) however is still missing and a new md-device md127 is appeard: Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [linear] md127 : active raid1 sda1[0] sdb1[1] 200704 blocks [2/2] [UU] md2 : active raid1 sda3[0] sdb3[1] 139243264 blocks [2/2] [UU] md1 : active (auto-read-only) raid1 sda2[0] sdb2[1] 4192896 blocks [2/2] [UU] unused devices: <none> The /etc/mdadm.conf is unchanged: DEVICE partitions ARRAY /dev/md0 level=raid1 UUID=081a1bd5:d2cfebd3:3d5369e9:2c7af0a6 ARRAY /dev/md1 level=raid1 UUID=6c203ec1:9360f8ba:da20cf36:64ef942c ARRAY /dev/md2 level=raid1 UUID=96498c7c:8cac6295:1f678b78:d723672a I was hesitating, using the UUID's of the physical devices within the md-config because of one big disadvantage: In case of a disk replacement of the raid-systems, it would be more cumbersome to fix the raid-devices. The patch for setup-md.sh did not solve my original problem, the missing md0-device. From my perspective it neither harms nor helps applying the setup-md.sh patch (Attachment 262365 Details for Bug 461673). Let's see, what the official solution will look like. Thank you for your help -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c24 --- Comment #24 from Michal Marek <mmarek@novell.com> 2009-02-21 08:57:16 MST --- I didn't reproduce the bug, but the patch from comment #6 is obviously safe, so I added it to Factory and 11.1 mdadm. I just hope we are not hiding another bug with this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User xwhu@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c25 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #25 from Xinwei Hu <xwhu@novell.com> 2009-03-11 01:12:13 MST --- Thanks Michal, closing it as Fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=461673 User swamp@suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c26 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.1:23137 --- Comment #26 from Swamp Workflow Management <swamp@suse.com> 2009-03-30 05:16:24 MDT --- Update released for: mdadm Products: openSUSE 11.1 (debug, i586, ppc, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com