All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephan Windmüller" <stephan.windmueller-ogaGWlaKng3jEoi5djuKH7NAH6kLmebB@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Device or resource busy
Date: Mon, 27 Oct 2008 14:10:34 +0100	[thread overview]
Message-ID: <20081027131034.GC25001@speutel.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

Hello!

On our Ubuntu (8.04) machine we mount home directories from a Solaris
server with NFS and autofs. From time to time users complain that they
are unable to delete any directories. The error message is "Device or
resource busy".

When I look with "nfsstat -m", I can see a lot of mount points for each
user, including the directory which cannot be deleted. One user had a
total of 200 mounts!

My question is: Why does NFS mount each directory seperately?

Here is an example output for a user:

/ldaphome/username from host:/export/username
 Flags: rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,
 proto=tcp,timeo=600,retrans=2,sec=sys,addr=host

TIA
 Stephan

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2321 bytes --]

             reply	other threads:[~2008-10-27 13:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 13:10 Stephan Windmüller [this message]
     [not found] ` <20081027131034.GC25001-YXCdMCmAy7qELgA04lAiVw@public.gmane.org>
2008-10-27 14:01   ` Device or resource busy Trond Myklebust
     [not found]     ` <1225116112.7842.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-10-27 14:29       ` Stephan Windmüller
     [not found]         ` <20081027142944.GD25001-YXCdMCmAy7qELgA04lAiVw@public.gmane.org>
2008-10-27 15:01           ` Trond Myklebust
     [not found]             ` <1225119712.14242.10.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-10-29 15:09               ` Stephan Windmüller
     [not found]                 ` <20081029150927.GE13990-YXCdMCmAy7qELgA04lAiVw@public.gmane.org>
2008-10-29 15:58                   ` Andy Adamson
  -- strict thread matches above, loose matches on Subject: below --
2015-01-20 12:28 Rohit Kulkarni
2015-01-20 19:44 ` Alexander Aring
2015-01-21 10:30   ` Rohit Kulkarni
2015-01-21 11:58     ` Maciej Wasilak
     [not found]       ` <54bf9983.07f4440a.7103.0a2e@mx.google.com>
     [not found]         ` <CAFUtXGx-naVAhPOM4OEQt9EoJEQ7NiiG7ni3kxd5zzsiNT52iA@mail.gmail.com>
     [not found]           ` <54bfa40a.c51e460a.6035.ffff8290@mx.google.com>
     [not found]             ` <CAFUtXGwbcBF=90bZtwJ26AWaoSoOvxnxotikjwfNcNfhAjEaOQ@mail.gmail.com>
2015-01-21 13:34               ` Rohit Kulkarni
2015-01-21 15:46         ` Alexander Aring
2015-01-22  7:59           ` Rohit Kulkarni
2015-01-22 20:59             ` Alexander Aring
2015-01-22 21:58               ` Maciej Wasilak
2015-01-22 22:20                 ` Alexander Aring
2015-01-23  7:59                   ` Alexander Aring
2015-01-25 11:36                     ` Maciej Wasilak
2015-01-25 15:24                       ` Alexander Aring
2015-01-27  9:24                       ` Rohit Kulkarni

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=20081027131034.GC25001@speutel.de \
    --to=stephan.windmueller-ogagwlakng3jeoi5djukh7nah6klmebb@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /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.