linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: AMIT SAHRAWAT <a.sahrawat@samsung.com>
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"namjae.jeon@samsung.com" <namjae.jeon@samsung.com>
Subject: Re: [Problem]NFS Server – Umount results in Device Busy.
Date: Thu, 10 May 2012 06:38:08 -0400	[thread overview]
Message-ID: <20120510103807.GA32608@fieldses.org> (raw)
In-Reply-To: <32336989.330131336633170527.JavaMail.weblogic@epml01>

On Thu, May 10, 2012 at 06:59:32AM +0000, AMIT SAHRAWAT wrote:
> Linux Kernel: 2.6.35.14
>  
> We are using NFS for data transfer from one target to another target.
> On Server we are using 3 mount points – to be used by application. And they are mentioned in /etc/exports
>  
> When initially just NFS Server is started -We can mount and safely un-mount the NFS mount point.
> Now, when NFS client is started and we mount at the client. Without doing any IO – if we do un-mount at the NFS Client –it un-mounts safely.
> But – when tried to un-mount the device at the NFS server – it results in error “Device Busy”
> “umount: can't umount /mnt: Device or resource busy”
>  
> Now , in order to umount the device -  we have to kill the process ‘nfsd’ – and then it un-mounts easily.
>  
> As per our understanding – it should not be an issue with the un-mount when it is not being used and also there should be no dependency to kill ‘nfsd’ to un-mount the device.
>  
> It leads to problem of killing ‘nfsd’ and restarting it – to make other mount points work without issue.
>  
> Is there any method to un-mount the device without getting this ‘BUSY’ error? Or can we kill only nfsd service which was using that mount point?

If all the clients unmount, and then you run "exportfs -f" on the
server, you'll probably find you can then unmount the export.

But stopping nfsd is the most reliable way to ensure you can unmount the
exported filesystems.  I'd recommend doing that using your distro's nfs
scripts (so "service nfs stop" or "systemctl nfs-server.service stop" or
equivalent) rather than killing nfsd yourself.

--b.

> Please share your input on the solution to the above problem. Is this expected behavior?

  reply	other threads:[~2012-05-10 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10  6:59 [Problem]NFS Server – Umount results in Device Busy AMIT SAHRAWAT
2012-05-10 10:38 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-07  7:47 Re: " Namjae Jeon
2012-06-07  8:13 ` Boaz Harrosh
2012-06-07  9:43   ` Namjae Jeon
2012-06-07 10:16     ` Boaz Harrosh
2012-06-07 10:36       ` Namjae Jeon
2012-06-07 11:33   ` J. Bruce Fields
2012-06-07 21:59     ` Boaz Harrosh
2012-06-07 22:05       ` Boaz Harrosh
2012-06-08  7:23       ` Namjae Jeon
2012-06-11 12:28       ` J. Bruce Fields
2012-06-07 23:41     ` Namjae Jeon

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=20120510103807.GA32608@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=a.sahrawat@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=namjae.jeon@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).