public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Harald Braumann <harry@unheit.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Deadlock on concurrent remount-ro and mdadm --stop (2.6.37)
Date: Tue, 25 Jan 2011 08:57:58 +1000	[thread overview]
Message-ID: <20110125085758.06df5e3e@nbeee.brown> (raw)
In-Reply-To: <20110123161500.GB4108@nn.nn>

On Sun, 23 Jan 2011 17:15:00 +0100
Harald Braumann <harry@unheit.net> wrote:

> On Fri, Jan 21, 2011 at 01:47:54PM +0100, Harald Braumann wrote:
> > On shutdown `umountroot' and `mdadm-raid'  are executed
> > concurrently. The actual commands are:
> > mount -o remount,ro /
> > mdadm --stop --scan
> > 
> > This seems to trigger a deadlock in the kernel. Dumping blocked
> > tasks (sysrq-W) gives:
> > 
> > md126_raid5: call trace:
> >   md_super_wait
> >   autoremove_wake_function
> >   bitmap_unplug
> >   ...
> > 
> > mount: call trace:
> >   sync_page
> >   io_schedule
> >   sync_page
> 
> I've now disable parallel boot in my system, so umountroot and mdadm
> shouldn't be called cuncurrently anymore. But I still get lock-ups on
> mdadm --stop. Umountroot is called before mdadm --stop, and all other
> filesystems are unmounted before that, so I guess
> there should be no `sync_page' in progress anymore. But I also have
> swap on the raid, so maybe there's a problem?
> 
> As not even the magic SysRQ keys work, I can't provide any more
> details. Any suggestions how I could debug this problem?

Thanks for the bug report.
Extra useful details would include:
 cat /proc/mdstat
 cat /proc/mounts

i.e. what is the exact configuration of the RAID or RAIDs, and where
are they mounted.

Thanks,
NeilBrown

  reply	other threads:[~2011-01-24 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 12:47 Deadlock on concurrent remount-ro and mdadm --stop (2.6.37) Harald Braumann
2011-01-23 16:15 ` Harald Braumann
2011-01-24 22:57   ` Neil Brown [this message]
2011-01-26  0:05     ` Harald Braumann
2011-01-26 21:31     ` Harald Braumann

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=20110125085758.06df5e3e@nbeee.brown \
    --to=neilb@suse.de \
    --cc=harry@unheit.net \
    --cc=linux-kernel@vger.kernel.org \
    /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