From: Spelic <spelic@shiftmail.org>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
linux-lvm@redhat.com
Subject: Re: DM / LVM hangs if snapshot present on kernel v3.0.3
Date: Tue, 21 Feb 2012 11:22:03 +0100 [thread overview]
Message-ID: <4F43704B.50903@shiftmail.org> (raw)
In-Reply-To: <4F428012.6090302@redhat.com>
On 02/20/12 18:17, Zdenek Kabelac wrote:
> Dne 20.2.2012 16:09, Spelic napsal(a):
>> On 02/20/12 14:51, Mike Snitzer wrote:
>>> I've never seen this. Which distro are you using?
>> Ubuntu 11.04 64-bit but with vanilla 3.0.3 kernel
>>
>> Ubuntu's lvm:
>> # lvm version
>> LVM version: 2.02.66(2) (2010-05-20)
>> Library version: 1.02.48 (2010-05-20)
>>
> So I'd guess you might be a 'victim' of Debian home-brew udev rules for lvm2,
> which were unfortunately not consulted with upstream (nor udev, nor lvm).
Indeed I have had a few bad experiences with Ubuntu's udev rules, but
never like this...
I don't think a wrong udev rule can hangup the whole machine with such
symptoms, you really think so?
- lvs and/or "lvchange --refresh ..." processes hanging forever in
kernel code (and AFAIR it was in DM region, that's the /proc/pid/stack
trace which I unfortunately lost)
- "sync" also cannot complete, so I can only do force reboot without flush
WARNING: multiple messages have this Message-ID (diff)
From: Spelic <spelic@shiftmail.org>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
linux-lvm@redhat.com
Subject: Re: [linux-lvm] DM / LVM hangs if snapshot present on kernel v3.0.3
Date: Tue, 21 Feb 2012 11:22:03 +0100 [thread overview]
Message-ID: <4F43704B.50903@shiftmail.org> (raw)
In-Reply-To: <4F428012.6090302@redhat.com>
On 02/20/12 18:17, Zdenek Kabelac wrote:
> Dne 20.2.2012 16:09, Spelic napsal(a):
>> On 02/20/12 14:51, Mike Snitzer wrote:
>>> I've never seen this. Which distro are you using?
>> Ubuntu 11.04 64-bit but with vanilla 3.0.3 kernel
>>
>> Ubuntu's lvm:
>> # lvm version
>> LVM version: 2.02.66(2) (2010-05-20)
>> Library version: 1.02.48 (2010-05-20)
>>
> So I'd guess you might be a 'victim' of Debian home-brew udev rules for lvm2,
> which were unfortunately not consulted with upstream (nor udev, nor lvm).
Indeed I have had a few bad experiences with Ubuntu's udev rules, but
never like this...
I don't think a wrong udev rule can hangup the whole machine with such
symptoms, you really think so?
- lvs and/or "lvchange --refresh ..." processes hanging forever in
kernel code (and AFAIR it was in DM region, that's the /proc/pid/stack
trace which I unfortunately lost)
- "sync" also cannot complete, so I can only do force reboot without flush
next prev parent reply other threads:[~2012-02-21 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 2:27 DM / LVM hangs if snapshot present on kernel v3.0.3 Spelic
2012-02-19 2:27 ` [linux-lvm] " Spelic
2012-02-19 10:00 ` [linux-lvm] [dm-devel] " Zdenek Kabelac
2012-02-20 13:51 ` Mike Snitzer
2012-02-20 13:51 ` [linux-lvm] " Mike Snitzer
2012-02-20 15:09 ` Spelic
2012-02-20 15:09 ` [linux-lvm] " Spelic
2012-02-20 17:17 ` Zdenek Kabelac
2012-02-20 17:17 ` [linux-lvm] " Zdenek Kabelac
2012-02-21 10:22 ` Spelic [this message]
2012-02-21 10:22 ` Spelic
2012-02-21 11:08 ` Zdenek Kabelac
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=4F43704B.50903@shiftmail.org \
--to=spelic@shiftmail.org \
--cc=dm-devel@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=snitzer@redhat.com \
--cc=zdenek.kabelac@gmail.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.