Mark, thanks for your comments. I have a SUSE SLES maintenance plan but no support agreement so I can't report a problem (as far as I know). Is there a channel where someone without a support agreement can report a problem?
Aria -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post Sent: Wednesday, June 01, 2011 11:12 AM To: [email protected] Subject: Re: mdadm message 'wrong state in superblock' at boot >>> On 6/1/2011 at 08:54 AM, Aria Bamdad <[email protected]> wrote: > Looking around, I found > > http://lists.gnu.org/archive/html/grub-devel/2010-07/msg00230.html > > which seems to be the exact problem. Has anyone somehow resolved this issue > on SUSE SLES 11 with SP1? There was an update for mdadm recently but it > didn't fix this issue. If no one opens a service request to fix it, it won't get fixed until SLES12 when package upgrades will occur. > This problem doesn't exist in SLES 10 and it seems > to happen in mdadm version 3.3. I want to know if I am safe using an md > device with this bug in mdadm. I can't tell from the various discussions in the thread you pointed at to be sure. I wouldn't bet any real important data on that setup. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
