Sponsored Content
Operating Systems Solaris NFS with a NAS: permanently inconsistent directory state across clients Post 302938966 by cosmojetz on Friday 20th of March 2015 11:19:55 AM
Old 03-20-2015
The inode number of the problem file in question is: 1080094

Yes, the NFS server is Linux-based.

Re. ensure mount points are 755: yes, they are; otherwise I wouldn't be able to create any directories/files. Note that the problem occurs only with some newly created directories, but when it does occur, it is consistent (directory can never be read).

Regarding the other problem (perhaps related): even with freshly mounted nfs dirs, the two clients show different group permissions for all files/dirs:

Example of same dir:
Client1:
drwxrwx---+ 58 user group
Client2:
drwx------+ 58 user group

Both user and group are defined with same ids in /etc/passwd, /etc/group. What config might be faulty to warrant this behavior?

Thanks.
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NFS to NAS transfer

Hey guys, My servers run Solaris 10. I have to move data from my NFS mount drives into the NAS storage area with all the same permissions ( for the users and programs and everything else). Can any one help me please ?? Thanks. MisterKhan (0 Replies)
Discussion started by: MisterKhan
0 Replies

2. UNIX for Dummies Questions & Answers

NFS mount of Windows NAS

The UPS connected to the Disk Array portion of my Windows 2003 NAS burned up over the weekend. Reconnected it to a new UPS and re-booted the NAS box. Since then I have not been able to get my HPUX 10.2 box to mount the shared drives on the NAS. At boot, the NFS client & server subsystems do a... (0 Replies)
Discussion started by: twalker0
0 Replies

3. UNIX for Advanced & Expert Users

Quest on NFS with 1 Server & 2 Clients

Hello; I work now with a team which has based her "applications" on the following schema: 1 NFS client C1 (linux redhat 5) writes a file fic.dat on a NFS SERVER S (RH 5) Another NFS client C2 is waiting for the same file fic.dat (on NFS server S1), and, when "fic.dat" appears, then makes... (8 Replies)
Discussion started by: SolarMax
8 Replies

4. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

5. UNIX for Dummies Questions & Answers

Unmounting NFS idle clients from server

Hello World, We have a software repository server in our environment which we use as an NFS server. Now this has been going on well before I was hired. Now, I observed many users not unmounting the NFS resources after their use. I ran showmount and it showed 513 current sessions. :wall: Is... (7 Replies)
Discussion started by: satish51392111
7 Replies

6. UNIX for Dummies Questions & Answers

NFS / DAS / SAN / NAS - Which is best?

i've used only NFS and as many already found out, it can be or rather i should say, it is very unreliable. based on the collective experiences of the members on this board, i would really appreciate it if someone can tell me what the next best file sharing method is? is it DAS? SAN? NAS? ... (1 Reply)
Discussion started by: SkySmart
1 Replies

7. Red Hat

Add directory to path permanently

I ssh in and am trying to add a directory permanently to $PATH in centos 7 and having issues. My current $PATH is echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin but when I do a sudo nano ~/.bashrc # .bashrc # User specific aliases and functions alias... (7 Replies)
Discussion started by: cmccabe
7 Replies

8. Shell Programming and Scripting

Solaris 9 Home Directory, Two Machines Sharing a NAS

Good Morning, I have 2 Solaris 9 machines sharing a NAS, and need to have users to be able to log in from the 2nd machine and get to all of their files on the NAS that were created on the 1st machine. So far its working ok, but when users log in to the second machine, their user IDs show... (20 Replies)
Discussion started by: Stellaman1977
20 Replies
userdel(1M)															       userdel(1M)

NAME
userdel - delete a user login from the system SYNOPSIS
alternate_password_file] login DESCRIPTION
The command deletes a user login from the system by modifying the appropriate login related files. The command requires the login argument. login is the name to be deleted, specified as a string of printable characters. It may not con- tain a colon or a newline Refer to usergroupname(5) to understand the functionality changes with the Numeric User Group Name feature. Options recognizes the following options: The home directory of login is removed from the system. This directory must exist. Following the successful execution of this command, none of the files and directories under the home directory will be available. If a user is deleted and the home directory is shared by others, then this directory is not deleted even with the option. Force the changes, even if the login is currently in use. Specify that the changes are being made to the alternate password file of NIS specified by the option. The and options should not be used with this option. Specify the path of the alternate password file of NIS. The option is used with the option. In the event where a directory is shared by users of the same group and the owner of that directory is deleted, then the ownership of that directory is propagated to the next user who is sharing that directory. The new owner is determined by looking at the order in which the users sharing this directory are added to the file. If there is only one user remaining then the directory is brought back to unshared mode by resetting the permissions to from NIS This command is aware of NIS user and group entries. Only local users and groups may be deleted or modified with this command. Attempts to delete or modify NIS users or groups will result in an error. NIS users and groups must be administered from the NIS server. The com- mand may fail with the error (return value 6) if the user specified is an NIS user (see passwd(4)). The error (return value 10) is returned if a local user belongs to an NIS group (see group(4)). NFS Errors may occur with the option if the affected directory is within an NFS mounted file system that does not allow root privileges across the NFS mount, and the directory or files within the directory do not have sufficient permissions. RETURN VALUE
exits with one of the following values: Successful completion. Invalid command syntax. Invalid argument supplied to an option. The login to be removed does not exist. The login to be removed is in use. Cannot modify the file, but the login was removed from the file. Unable to remove or modify the home directory. Unable to open file or file is non-existent. file or file busy. Another command may be modifying the file. Cannot delete entry from file. Out of memory. Invalid template file. EXAMPLES
Remove the user from the system: Remove the user from the system and delete home directory from the system: WARNINGS
Because many users may try to write the file simultaneously, a password locking mechanism was devised. If this locking fails after subse- quent retrying, terminates. FILES
Shadow Password file System Password file System group file Lock file used when updating password file SEE ALSO
passwd(1), users(1), groupadd(1M), groupdel(1M), groupmod(1M), logins(1M), useradd(1M), usermod(1M), group(4), passwd(4), shadow(4), user- groupname(5). STANDARDS CONFORMANCE
userdel(1M)
All times are GMT -4. The time now is 03:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy