All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
	device-mapper development <dm-devel@redhat.com>,
	linux-fsdevel@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>
Subject: Re: 2.6.35 causes deadlock when snapshotting root lv
Date: Fri, 18 Jun 2010 14:19:44 -0500	[thread overview]
Message-ID: <4C1BC6D0.2030203@sandeen.net> (raw)
In-Reply-To: <4C1BC125.4090902@sandeen.net>

Eric Sandeen wrote:
> Phillip Susi wrote:
>> On 06/17/2010 12:27 PM, Mike Snitzer wrote:
>>>>> http://git.kernel.org/linus/18e9e5104fcd9a9
>>>>> http://git.kernel.org/linus/6b0310fbf087ad6
>>>> Yes, these do look suspicious.  I'll test reverting them tonight.
>>> OK, I'd suggest reverting the VFS change (18e9e5104fcd9a9) first.
>> Turns out it was 6b0310fbf087ad6 that did it.  CCing Eric Sandeen since
>> he wrote it.  Eric, this patch seems to cause a deadlock when taking an
>> lvm snapshot of the root lv.  Any idea why?
> 
> I'll look.  A sysrq-w when it hangs up would probably be enlightening...
> 
> -Eric

FWIW simple freeze/unfreeze works for me, and lvm snap on a non-root ext4
partition seems to as well.  I'm out for a few days and probably won't
get a root lv set up to test anytime soon.  If you can provide sysrq-w
output that probably will be a big help if it doesn't end up being obvious
by inspection.  :)

Thanks
-Eric

  reply	other threads:[~2010-06-18 19:19 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
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 [this message]
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=4C1BC6D0.2030203@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=dm-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=psusi@cfl.rr.com \
    --cc=sandeen@redhat.com \
    --cc=snitzer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.