Linux NFS development
 help / color / mirror / Atom feed
From: "Stephan Windmüller" <stephan.windmueller-ogaGWlaKng3jEoi5djuKH7NAH6kLmebB@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Device or resource busy
Date: Mon, 27 Oct 2008 15:29:44 +0100	[thread overview]
Message-ID: <20081027142944.GD25001@speutel.de> (raw)
In-Reply-To: <1225116112.7842.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

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

On Mon, 27. Oct 2008, Trond Myklebust wrote:

> > 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!
> If /export/username is on a different volume from /export on the server,
> then the NFS client has to mount it as being a different volume on the
> client. 'cat /proc/fs/nfsfs/volumes' should be able to tell you if your
> server is exporting more than one volume.

/export and /export/home/username are different volumes, but I only
share /export/home/username. Also it is not only the homedirectory
itself but many subdirectories which cause this error. A sample output
from 'nfsstat -m':

-----

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

/home/username/workspace/ls5/da/text/Konzept from
fileserver:/export/home/username/workspace/ls5/da/text/Konzept
 Flags: rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=fileserver

/home/username/.eclipse/org.eclipse.platform_3.3.0_1148896627 from
fileserver:/export/home/username/.eclipse/org.eclipse.platform_3.3.0_1148896627
 Flags: rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=fileserver

[...]

-----

The output from /proc/fs/nfsfs/volumes looks like:

NV SERVER   PORT DEV     FSID
v3 81d91add  801 0:29    1000001009f:0
v3 81d91add  801 0:27    1000001010f:0
v3 81d91ade  801 0:30    100000100f1:0
v3 81d91add  801 0:31    1000001018b:0
v3 81d91add  801 0:26    10000010189:0
v3 81d91ade  801 0:28    100000100ef:0
v3 81d91ade  801 0:32    100000100f6:0
v3 81d91add  801 0:33    10000010192:0

- Stephan

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

  parent reply	other threads:[~2008-10-27 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 13:10 Device or resource busy Stephan Windmüller
     [not found] ` <20081027131034.GC25001-YXCdMCmAy7qELgA04lAiVw@public.gmane.org>
2008-10-27 14:01   ` Trond Myklebust
     [not found]     ` <1225116112.7842.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-10-27 14:29       ` Stephan Windmüller [this message]
     [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

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=20081027142944.GD25001@speutel.de \
    --to=stephan.windmueller-ogagwlakng3jeoi5djukh7nah6klmebb@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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