From: Daniel Stodden <daniel.stodden@citrix.com>
To: Andreas Olsowski <andreas.olsowski@leuphana.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: hanging tapdisk2 processes and improper udev rules
Date: Fri, 22 Jul 2011 02:32:36 -0700 [thread overview]
Message-ID: <1311327158.2360.15.camel@ramone> (raw)
In-Reply-To: <1311327074.2360.14.camel@ramone>
On Fri, 2011-07-22 at 05:31 -0400, Daniel Stodden wrote:
> On Fri, 2011-07-22 at 05:18 -0400, Andreas Olsowski wrote:
> > When i xl-create a guest, i get one message per assigned block device:
> >
> > root@xenturio1:/var/log# xl create /etc/xen/domains/x1test.sxp
> > Parsing config file /etc/xen/domains/x1test.sxp
> > Daemon running with PID 8704
>
> Can you try if it gets better when removing that file?
The udev rules, in case it isn't clear :)
Daniel
> Thanks,
> Daniel
>
> > root@xenturio1:/var/log# tail -10 error |grep SYMLINK
> > syslog:Jul 22 10:58:05 xenturio1 udevd[8658]: kernel-provided name
> > 'blktap2' and NAME= 'xen/blktap-2/blktap2' disagree, please use
> > SYMLINK+= or change the kernel to provide the proper name
> > syslog:Jul 22 10:58:05 xenturio1 udevd[8664]: kernel-provided name
> > 'blktap3' and NAME= 'xen/blktap-2/blktap3' disagree, please use
> > SYMLINK+= or change the kernel to provide the proper name
> >
> >
> > The guest works fine at that point.
> > root 8975 1.0 0.0 21664 3292 ? SLs 11:00 0:00 tapdisk2
> > root 8978 0.0 0.0 21008 916 ? S 11:00 0:00 udevd
> > --daemon
> > root 8981 0.0 0.0 21664 3256 ? SLs 11:00 0:00 tapdisk2
> > root 8983 0.0 0.0 21008 796 ? S 11:00 0:00 udevd
> > --daemon
> > root 9002 0.0 0.0 21008 800 ? S 11:00 0:00 udevd
> > --daemon
> > root 9020 0.0 0.0 35500 952 ? Ssl 11:00 0:00 xl
> > create /etc/xen/domains/x1test2.sxp
> > root 9067 0.0 0.0 0 0 ? S 11:00 0:00
> > [blkback.3.xvda1]
> > root 9068 0.0 0.0 0 0 ? S 11:00 0:00
> > [blkback.3.xvda2]
> >
> >
> >
> > Then i shutdown the guest:
> > root@xenturio1:/var/log# xl shutdown x1test
> >
> > And i am left with remaining tapdisk2 and udev processes, one for each
> > block device that was assigned to the guest:
> > root 8975 0.1 0.0 21664 3256 ? SLs 11:00 0:00 tapdisk2
> > root 8981 0.0 0.0 21664 3256 ? SLs 11:00 0:00 tapdisk2
> > root 8983 0.0 0.0 21008 796 ? S 11:00 0:00 udevd
> > --daemon
> > root 9002 0.0 0.0 21008 800 ? S 11:00 0:00 udevd
> > --daemon
> >
> > I am using Xen 4.1.1 with the 2.6.32.43-pvops kernel from jeremy.
> > My distro is debian 6.0.2. that uses udev 164-3.
> > I did update it on a different machine to 171-3, but that did not help.
> >
> >
> > My xen-backend.rules contains the default:
> > SUBSYSTEM=="xen", KERNEL=="blktap[0-9]*", NAME="xen/blktap-2/%k",
> > MODE="0600"
> > SUBSYSTEM=="blktap2", KERNEL=="blktap[0-9]*", NAME="xen/blktap-2/%k",
> > MODE="0600
> >
> >
> > My questions are:
> > - Are the two issues related?
> > - How can i fix them?
> >
> >
> > I think that eventually this will cause the host to run out of either
> > free process IDs and/or RAM.
> >
> >
>
>
next prev parent reply other threads:[~2011-07-22 9:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 9:18 hanging tapdisk2 processes and improper udev rules Andreas Olsowski
2011-07-22 9:28 ` Ian Campbell
2011-07-22 11:36 ` Andreas Olsowski
2011-07-22 14:07 ` Ian Campbell
2011-07-22 14:28 ` Andreas Olsowski
2011-07-22 14:32 ` Ian Campbell
2011-07-25 8:55 ` Andreas Olsowski
2011-08-11 13:32 ` Andreas Olsowski
2011-07-22 9:31 ` Daniel Stodden
2011-07-22 9:32 ` Daniel Stodden [this message]
2011-07-22 9:34 ` Sébastien RICCIO
2011-07-22 9:50 ` Daniel Stodden
2011-07-22 10:01 ` Sébastien RICCIO
2011-07-22 18:55 ` hanging tapdisk2 processes and multipathing Daniel Stodden
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=1311327158.2360.15.camel@ramone \
--to=daniel.stodden@citrix.com \
--cc=andreas.olsowski@leuphana.de \
--cc=xen-devel@lists.xensource.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.