public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [Problem]NFS Server – Umount results in Device Busy.
@ 2012-05-10  6:59 AMIT SAHRAWAT
  2012-05-10 10:38 ` J. Bruce Fields
  0 siblings, 1 reply; 2+ messages in thread
From: AMIT SAHRAWAT @ 2012-05-10  6:59 UTC (permalink / raw)
  To: Trond.Myklebust; +Cc: linux-nfs, linux-kernel, bfields, namjae.jeon@samsung.com

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=windows-1252, Size: 1410 bytes --]

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?
Please share your input on the solution to the above problem. Is this expected behavior?
 
Thanks & Regards,
Amit Sahrawatÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Problem]NFS Server – Umount results in Device Busy.
  2012-05-10  6:59 [Problem]NFS Server – Umount results in Device Busy AMIT SAHRAWAT
@ 2012-05-10 10:38 ` J. Bruce Fields
  0 siblings, 0 replies; 2+ messages in thread
From: J. Bruce Fields @ 2012-05-10 10:38 UTC (permalink / raw)
  To: AMIT SAHRAWAT
  Cc: Trond.Myklebust, linux-nfs, linux-kernel, namjae.jeon@samsung.com

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?

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-05-10 10:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-10  6:59 [Problem]NFS Server – Umount results in Device Busy AMIT SAHRAWAT
2012-05-10 10:38 ` J. Bruce Fields

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox