From: Avi Kivity <avi@redhat.com>
To: Sebastian Hetze <s.hetze@linux-ag.com>
Cc: kvm@vger.kernel.org
Subject: Re: syscall rmdir hangs with autofs
Date: Mon, 19 Jul 2010 16:09:12 +0300 [thread overview]
Message-ID: <4C444E78.8030907@redhat.com> (raw)
In-Reply-To: <20100719124847.0CDBBA005F@mail.linux-ag.de>
On 07/19/2010 03:48 PM, Sebastian Hetze wrote:
>
>> Looks like a false alarm then. The rmdir is waiting for the mount to
>> flush everything to disk, which is slow and takes a while.
>>
>> Does it return eventually?
>>
> No, it does not return within hours (>10). And the problem occurs only
> once in a while although the system is busy every day (and night)
> and automount is mounting/expiring frequently.
>
> I would expect the "/bin/umount dir" process (which is forked by
> automount if I read the code correctly) to return only after the flush
> is complete. So I expect the rmdir being called afterwards on an plain
> empty directory.
>
> BTW: the mount is just a bind mount, so no flush should be necessary
> anyway.
>
It looks like VFS breakage. Does this happen with older guest kernels?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-07-19 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 8:39 syscall rmdir hangs with autofs Sebastian Hetze
2010-07-19 11:12 ` Avi Kivity
2010-07-19 11:40 ` Sebastian Hetze
[not found] ` <20100719114034.62BDD30303F5@mail.linux-ag.de>
2010-07-19 12:21 ` Avi Kivity
2010-07-19 12:48 ` Sebastian Hetze
2010-07-19 13:09 ` Avi Kivity [this message]
2010-07-19 13:45 ` Sebastian Hetze
[not found] ` <20100719134558.A0CD2A005F@mail.linux-ag.de>
2010-07-19 14:00 ` Avi Kivity
2010-07-19 14:47 ` Sebastian Hetze
[not found] ` <20100719144750.334F2303001B@mail.linux-ag.de>
2010-07-19 15:03 ` Avi Kivity
2010-07-19 15:23 ` Sebastian Hetze
[not found] ` <20100719152518.641BAB001A@mail.linux-ag.de>
2010-07-19 15:28 ` Avi Kivity
2010-07-19 15:38 ` Sebastian Hetze
[not found] ` <20100719153816.1E33FB0016@mail.linux-ag.de>
2010-07-19 17:55 ` Avi Kivity
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=4C444E78.8030907@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=s.hetze@linux-ag.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.