From: Mike Snitzer <snitzer@redhat.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: device-mapper development <dm-devel@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: 2.6.35 causes deadlock when snapshotting root lv
Date: Thu, 17 Jun 2010 10:27:32 -0400 [thread overview]
Message-ID: <20100617142731.GA10071@redhat.com> (raw)
In-Reply-To: <4C1A2839.5010407@cfl.rr.com>
On Thu, Jun 17 2010 at 9:50am -0400,
Phillip Susi <psusi@cfl.rr.com> wrote:
> What:
>
> lvcreate -s -n snap -L 1g vg/root hangs in an unkillable state while
> trying to flush the fs and suspend the device to switch tables over to
> the snapshot, and no further IO is possible so the system must be hard
> booted with magic-sysrq.
>
> Where: 2.6.35, all 3 release candidates. 2.6.34 and earlier kernels are
> fine.
Which filesystem are you using? Which 2.6.35-rc?
There haven't been _any_ changes to DM for 2.6.35 (some DM fixes may get
pushed to Linus once Alasdair gets back from traveling).
So what this means is that the VFS (or ext4) freeze changes introduced
in 2.6.35 are the likely culprit:
http://git.kernel.org/linus/18e9e5104fcd9a9
http://git.kernel.org/linus/6b0310fbf087ad6
Though it could also be an issue with the various 2.6.35 writeback
changes (depending on which -rcX you're using).
Point is: this is not a DM regression.
Mike
next prev parent reply other threads:[~2010-06-17 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:50 2.6.35 causes deadlock when snapshotting root lv Phillip Susi
2010-06-17 14:27 ` Mike Snitzer [this message]
2010-06-17 16:16 ` Phillip Susi
2010-06-17 16:27 ` Mike Snitzer
2010-06-18 1:29 ` Phillip Susi
2010-06-18 18:55 ` Eric Sandeen
2010-06-18 19:19 ` Eric Sandeen
2010-06-18 19:23 ` Eric Sandeen
2010-06-23 19:37 ` [PATCH] ext4: fix freeze deadlock under IO Eric Sandeen
2010-08-01 21:41 ` Ted Ts'o
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=20100617142731.GA10071@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
/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).