From: Peter Rajnoha <prajnoha@redhat.com>
To: Joseph Graham <t67t67t67@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] can't make snapshot
Date: Fri, 16 Sep 2011 13:50:15 +0200 [thread overview]
Message-ID: <4E7337F7.1080201@redhat.com> (raw)
In-Reply-To: <CAPbm57VXFxPNgGwh-sNZcgBqq4HDFTg2H_uAMdsnR+xYQ14Cfw@mail.gmail.com>
On 09/16/2011 12:41 PM +0100, Joseph Graham wrote:
> lvcreate --size 100M --snapshot --name root_snap /dev/VolGroup00/root
> -vvv 2> outfile
>
> http://ompldr.org/vYWRqbg/outfile
I see:
"Uevent not generated! Calling udev_complete internally to avoid process lock-up."
in the log. This looks like a problem we've discovered recently. See also:
http://www.redhat.com/archives/dm-devel/2011-August/msg00075.html
That happens when namespaces are in play. This was also found while using
the Chrome web browser (which makes use of the namespaces for sandboxing).
Do you use Chrome web browser?
Peter
next prev parent reply other threads:[~2011-09-16 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 10:41 [linux-lvm] can't make snapshot Joseph Graham
2011-09-16 11:50 ` Peter Rajnoha [this message]
2011-09-16 11:52 ` Peter Rajnoha
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=4E7337F7.1080201@redhat.com \
--to=prajnoha@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=t67t67t67@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 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).