From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: syscall rmdir hangs with autofs Date: Mon, 19 Jul 2010 16:09:12 +0300 Message-ID: <4C444E78.8030907@redhat.com> References: <20100719083932.187C6303001B@mail.linux-ag.de> <4C44333B.5090709@redhat.com> <20100719114034.62BDD30303F5@mail.linux-ag.de> <4C444358.8010500@redhat.com> <20100719124847.0CDBBA005F@mail.linux-ag.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Sebastian Hetze Return-path: Received: from mx1.redhat.com ([209.132.183.28]:25059 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932291Ab0GSNJQ (ORCPT ); Mon, 19 Jul 2010 09:09:16 -0400 In-Reply-To: <20100719124847.0CDBBA005F@mail.linux-ag.de> Sender: kvm-owner@vger.kernel.org List-ID: 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