linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Maciej Naruszewicz <maciej.naruszewicz@intel.com>
Cc: linux RAID <linux-raid@vger.kernel.org>,
	Jes Sorensen <Jes.Sorensen@redhat.com>,
	Doug Ledford <dledford@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Dan Williams <dan.j.williams@intel.com>,
	"Dorau, Lukasz" <lukasz.dorau@intel.com>,
	Clint Byrum <clint@ubuntu.com>,
	"Danecki, Jacek" <jacek.danecki@intel.com>,
	"Patelczyk, Maciej" <maciej.patelczyk@intel.com>,
	"Tomczak, Marcin" <marcin.tomczak@intel.com>
Subject: Re: mdadm-3.2.5 coming soon :-(
Date: Thu, 17 May 2012 15:44:49 +1000	[thread overview]
Message-ID: <20120517154449.2eeb0512@notabene.brown> (raw)
In-Reply-To: <4FB274B3.8040907@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]

On Tue, 15 May 2012 17:22:27 +0200 Maciej Naruszewicz
<maciej.naruszewicz@intel.com> wrote:

> > If anyone knows of any other issues that have cropped up wit 3.2.4, please
> > let me know.
> >
> > Thanks,
> > NeilBrown
> 
> Since mdadm-3.2.4 creating volumes using IMSM containers is impossible 
> (segfaults), unless the kernel is 3.1.x or higher (for instance 
> everything SEEMS to work in RHEL 7.0 Alpha and openSUSE 12.1). Full 
> story from SLES 11 SP2 (kernel-3.0.13-0.27-default) with mdadm-3.2.4 :
> 
> $ mdadm --zero-superblock /dev/sd[cd]
> $ mdadm -C /dev/md/imsm0 -a md -e imsm -n 2 /dev/sd[cd] -R
> 
>      [...]
> 
> $ tail /var/log/messages
> 
>      May 15 17:16:10 gklab-128-174 kernel: [  317.653470] md: bind<sdc>
>      May 15 17:16:10 gklab-128-174 kernel: [  317.653519] md: bind<sdd>
>      May 15 17:16:11 gklab-128-174 udevd-work[5249]: '/sbin/mdadm 
> --detail --export /dev/md127' unexpected exit with status 0x000b
>      May 15 17:16:11 gklab-128-174 kernel: [  317.701434] mdadm[5250]: 
> segfault at 78 ip 0000000000450c4f sp 00007fff6c99ada0 error 4 in 
> mdadm[400000+69000]
> 
> $ mdadm -C /dev/md/raid1_2disks -a md -l 1  --size 1500000 -n 2 
> /dev/sd[cd] -R -f
> 
>      mdadm: cannot open device: 11:0
>      [...]
>      mdadm: cannot open device: 11:0
>      [...]
>      Segmentation fault
> 
> $ tail /var/log/messages
> 
>      May 15 17:18:36 gklab-128-174 kernel: [  463.291235] mdadm[5298]: 
> segfault at 78 ip 0000000000450c4f sp 00007fff8ad887e0 error 4 in 
> mdadm[400000+69000]
> 
> Similiar story in RHEL 6.3 Beta, those errors don't happen with kernel 
>  >= 3.1.x though (or mdadm-3.2.3 :)).
> 
> Maciek N

Could the difference be that fact that 3.2.4 default to using /run, which
doens't exist on SLES11 and may on in RHEL 6.3?
If you compile with
   make MAP_DIR=/var/run/mdadm
does it work better?

However I think this will fix the crash you are seeing.

diff --git a/mapfile.c b/mapfile.c
index b890ed2..70ff355 100644
--- a/mapfile.c
+++ b/mapfile.c
@@ -404,6 +404,8 @@ void RebuildMap(void)
 			if (ok != 0)
 				continue;
 			info = st->ss->container_content(st, subarray);
+			if (!info)
+				continue;
 
 			if (md->devnum >= 0)
 				path = map_dev(MD_MAJOR, md->devnum, 0);

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-05-17  5:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  4:22 Last call for input to mdadm-3.2.4 NeilBrown
2012-05-03  9:18 ` Jes Sorensen
2012-05-15 11:50 ` mdadm-3.2.5 coming soon :-( NeilBrown
2012-05-15 15:22   ` Maciej Naruszewicz
2012-05-17  5:44     ` NeilBrown [this message]
2012-05-17  8:28       ` Patelczyk, Maciej
2012-05-17 11:52         ` Patelczyk, Maciej
2012-05-18  3:44           ` NeilBrown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120517154449.2eeb0512@notabene.brown \
    --to=neilb@suse.de \
    --cc=Jes.Sorensen@redhat.com \
    --cc=clint@ubuntu.com \
    --cc=dan.j.williams@intel.com \
    --cc=dledford@redhat.com \
    --cc=jacek.danecki@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lukasz.dorau@intel.com \
    --cc=maciej.naruszewicz@intel.com \
    --cc=maciej.patelczyk@intel.com \
    --cc=marcin.tomczak@intel.com \
    --cc=mjt@tls.msk.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).