Sponsored Content
Operating Systems Solaris NFS: Cannot unshare directory. Post 302422349 by solaris_user on Tuesday 18th of May 2010 07:16:52 AM
Old 05-18-2010
did you tried manually force unmount ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

NFS mount home directory

Hello All, I have a question that I think I have the answer to but I'm not sure. All the information I get kind of dance around it. Well, my question is if you have NFS running, automount running, with auto_master and auto_home on a server. If a user logs in form cleint machine that has... (3 Replies)
Discussion started by: larry
3 Replies

2. UNIX for Advanced & Expert Users

Problem: Automounting Home directory for nis & nfs configuration doesn't work

Hi all, First of all, i am so sorry about my bad level in English writing. I have some problem in linux and i hope the experts of this forum to help me if they have enough time to reply to me. I have a scenario of configuring NIS and NFS in Redhat Linux environment such that user can login... (0 Replies)
Discussion started by: pioneer
0 Replies

3. Programming

Not able to use NFS mounted directory as buffer for untar & unzip.

Hi, For a new requirement, we are trying to use NFS mounted directory as the buffer (TMP_DIR) for untar. Target OS- VxWorks Host OS - Windows Embedded. mounted a directory in wondows onto VxWorks. During untar process of GNU we come across utime, for chaning the time stamp of the... (0 Replies)
Discussion started by: suraj.bc
0 Replies

4. UNIX for Advanced & Expert Users

NFS export need to be able to write to directory but not list

My issue is I want an NFS share where I can write to the directory, but not list any of the files in there. (doesn't matter if someone knows the name can open the file). Have an NFS export for example: drwxrwxrw- 2 cranes staff 256 18 May 12:48 cranes The export will only... (1 Reply)
Discussion started by: Cranie
1 Replies

5. Solaris

zfs cannot unmount (cannot unshare)

I have installed Solaris 11 Express on my machine, created a raidz2 zpool named shares and set up sharing (zfs set sharesmb=on shares). I also created a script for automatic backuping using snapshots. Everything worked fine. But yesterday I tried recovering from one of those backuped snapshots:... (1 Reply)
Discussion started by: RychnD
1 Replies

6. Solaris

Strange thing with solaris ls on nfs shared directory

I shared from linux server a dir with nfs3,solaris mount ok,and can tar files,but if i do ls or cp.. on mnt i have mount the nfs share root@solaris: mnt $ touch 2 root@solaris: mnt $ ls -lh ls: can't read ACL on .: Permission denied root@solaris: mnt $ ls 1.tar 2 root@solaris: mnt $ cp... (4 Replies)
Discussion started by: Linusolaradm1
4 Replies

7. UNIX for Advanced & Expert Users

Mounting a directory using nfs version4

Hi, I would like to know how can we mount a directory using nfs v4 ? When I use the below command, I am not sure what nfs version am using to mount the directory. mount -t <server_name>:<shared_directory> <shared_directory>. eg: mount -t 10.50.0.8:/home/arun/mount/share_dir... (7 Replies)
Discussion started by: arunsriniv
7 Replies

8. Solaris

ZFS shared with NFS makes directory cover filesystem

I'm having a strange issue that I'm unsure what to do with. I have a new Solaris home server that I want hard mount /home to all our servers. I've made each user's home directory a filesystem so that I can manage every user with a quota. In each one of my server vfstab files I have it set as: ... (4 Replies)
Discussion started by: mijohnst
4 Replies

9. Solaris

NFS with a NAS: permanently inconsistent directory state across clients

Hi, I am having some NFS directory consistency problems with the below setup on a local (192.) network: 1. Different permissions (chmod) for the same NFS dir are reflected on different clients. 2. (more serious) an NFS dir created on client1 cannot be accessed on client2; this applies to some... (10 Replies)
Discussion started by: cosmojetz
10 Replies

10. HP-UX

Unable to write to NFS mounted directory

Hi, I have exported a few nfs mounts from one server to the nfs clients. This is my nfs server dfstab : # cat /etc/dfs/dfstab # place share(1M) commands here for automatic execution # on entering init state 3. # # share <pathname> # .e.g, # share -F... (3 Replies)
Discussion started by: anaigini45
3 Replies
umount(2)							System Calls Manual							 umount(2)

NAME
umount(), umount2() - unmount a file system SYNOPSIS
DESCRIPTION
requests that a previously mounted file system contained on the block special device identified by name be unmounted. requests that a previously mounted file system contained on the block special device identified by name be unmounted in the manner described in flags. name is a pointer to a path name. flags is a bitmask of flags, specified in that are combined to describe the type of unmount to be performed. Valid flags are: perform a normal unmount perform a forced unmount MS_NORMAL and MS_FORCE are mutually exclusive. A forced unmount is one which will occur regardless of activity on the file system. After unmounting the file system, the directory upon which the file system was mounted reverts to its ordinary interpretation. and can also request that a file system mounted previously on the directory identified by name be unmounted. After unmounting the file system, name reverts to its ordinary interpretation. and can be invoked only by the user with the appropriate privilege. NETWORKING FEATURES
NFS path must indicate a directory name when unmounting an NFS file system. RETURN VALUE
If successful, and return a value of Otherwise, they return a value of -1 and set to indicate the error. ERRORS
and fail if one or more of the following are true: A component of the path prefix of name denies search permission. A file on name is busy. name points outside the allocated address space of the process. Reliable detection of this error is implementation dependent. name is not mounted. flags is not a valid combination of flags. Too many symbolic links were encountered in translating the path name. name exceeds bytes, or a component of name exceeds bytes while is in effect. name does not exist. name is null. A forced unmount was requested on a file system that does not support it. name is not a block special device. A component of name is not a directory. The device associated with name does not exist. The effective user ID of the process is not that of a user with appropriate privileges. SEE ALSO
mount(1M), mount(2), privileges(5). STANDARDS CONFORMANCE
umount(2)
All times are GMT -4. The time now is 09:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy